linux-kernel - Re: [PATCH 0/4] kaslr: extend movable_node to movable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <cf340654-39e2-af23-ef9a-156d097a6290@cn.fujitsu.com>
Date:   Fri, 20 Oct 2017 14:41:53 +0800
From:   Dou Liyang <douly.fnst@...fujitsu.com>
To:     Chao Fan <fanc.fnst@...fujitsu.com>
CC:     <linux-kernel@...r.kernel.org>, <x86@...nel.org>, <hpa@...or.com>,
        <tglx@...utronix.de>, <mingo@...hat.com>, <bhe@...hat.com>,
        <keescook@...omium.org>, <indou.takao@...fujitsu.com>,
        <caoj.fnst@...fujitsu.com>
Subject: Re: [PATCH 0/4] kaslr: extend movable_node to
 movable_node=nn[KMG]@ss[KMG]

Hi Chao,

[...]
>
> Thanks for that. I think likely() is suitable for another place.

Aha, Just as an example, don't need to use it. ;-)

>>>
>>> Both are OK. I think outputing the memory region in movable_node or
>>> immovable_node are both reasonable. So the interface of both methods
>>> will be useful. And after we decided which policy used in kaslr, then
>>> add the interface of /sys.

Yes, so great.

>>>
>>
>> Actually, I prefer the first one, are you ready to post the patches
>> for the first policy?
>>

I guess you may miss this, I want to know if you have already do the
first policy. then we can compare and decide which one is better. If
not, I can do that! let's make KASLR work well with node hot-plug
quickly.

cc Baoquan,

do you have any ideas, ;-)

Thanks,
	dou.