lkml.org 
[lkml]   [2018]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/3] x86/boot/KASLR: enhance randomness of kernel load addr when using GiB hugepage
On Thu, Sep 06, 2018 at 01:58:08PM +0800, Pingfan Liu wrote:
>On Thu, Sep 6, 2018 at 12:07 PM Chao Fan <fanc.fnst@cn.fujitsu.com> wrote:
>>
>> On Thu, Sep 06, 2018 at 10:36:19AM +0800, Pingfan Liu wrote:
>>
>> Hi Pingfan,
>>
>> >commit 747ff6265db4 ("x86/boot/KASLR: Skip specified number of 1GB huge
>> >pages when doing physical randomization (KASLR)") and commit
>> >9b912485e0e7 ("x86/boot/KASLR: Add two new functions for 1GB huge pages
>> >handling") prevent the physical load addr of kernel from spoiling a good
>> >candidate of GiB page. But the algorithm deterministicly chooses the most
>> >front GiB page for hugetlb, and sacrifices the randomness, which
>> >is the heart of the KASLR. This patch tries to enlarge the randomness in
>> >the cases where hugepages=X < the num Y of good candidate of GiB
>>
>> Yes, in some situations, if Y > X, the patch would reduce the
>> randomness. And to reserve a fixed 1G for huge page is not perfect
>> enouth.
>> But the the size of slot is so small, the size of memory is so big.
>>
>Yes, but this is the sense of a human,. and normally, we are protected
>against the attack from a program.
>

Well, in my opinion, the problem that Baoquan tried to fix exists
only when Y == X. If Y > X, I think the problem is not a big problem,
even though kernel breaks a good 1G memory for huge page, there are still
enough place left.

>> >page.
>> >To comparison, taking a typical KVM guest for example, the head 3GiB mem
>> >can not be used as GiB hugetlb. Denoting the total mem size as Z(GiB), when
>> >Z=5, then Y=2, assuming X=1, the randomness range before this patch is
>> >4GiB, after this patch is 5GiB, and get a 25% improvement of randomness.
>>
>> Such as your example,
>> in 4G, the probability every slot chosen is about 0.00049
>> in 5G, the probability every slot chosen is about 0.00039
>> Yes, you did improve 25% for randomness. But I wonder if it's worth to
>> improve from 0.00049 to 0.00039.
>>
>This is the case of least improvement.
>
>> If there is something wrong in my understanding, please let me know.
>>
>Yes, you get my idea. There are two factor worth to consider. The 1st
>one is the head 3GiB, if it can be reduce to 1GiB or 2GiB, then the

Yes, as you said, from a human's feeling, I think if there are more
than one thousand slots, the probability is small enough.
In some situations, your patch improve the randomness much. As for whether
it's worth to do, let's see how other people think.

Thanks,
Chao Fan

>randomness will have a great improvement. The 2nd one is the X, which
>also play a important role of the randomness.
>
>Thanks and regards,
>Pingfan
>
>> Thanks,
>> Chao Fan
>>
>> >If Z=6, then Y=3, assuming X=2, the improvement equals: 50%( 6/(6-2) - 1);
>> >assuming X=1, the improvement will be: 20% (6/(6-1) - 1)
>> >
>> >Cc: Thomas Gleixner <tglx@linutronix.de>
>> >Cc: Ingo Molnar <mingo@redhat.com>
>> >Cc: "H. Peter Anvin" <hpa@zytor.com>
>> >Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
>> >Cc: Baoquan He <bhe@redhat.com>
>> >Cc: Chao Fan <fanc.fnst@cn.fujitsu.com> (authored:1/16=6%)
>> >Cc: x86@kernel.org
>> >
>> >Pingfan Liu (3):
>> > x86/boot/KASLR: change the prototypes of
>> > process_efi_entries/process_e820_entries
>> > x86/boot/KASLR: change the prototype of process_mem_region() to meet
>> > the align requirement
>> > x86/boot/KASLR: enhance randomness when using GiB hugepage
>> >
>> > arch/x86/boot/compressed/kaslr.c | 228 ++++++++++++++++++++++++++-------------
>> > 1 file changed, 152 insertions(+), 76 deletions(-)
>> >
>> >--
>> >2.7.4
>> >
>> >
>> >
>>
>>
>
>


\
 
 \ /
  Last update: 2018-09-06 12:01    [W:0.078 / U:0.492 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site