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]
Date:   Thu, 3 Aug 2017 16:59:26 +0800
From:   Dou Liyang <douly.fnst@...fujitsu.com>
To:     Chao Fan <fanc.fnst@...fujitsu.com>,
        <linux-kernel@...r.kernel.org>, <x86@...nel.org>
CC:     <hpa@...or.com>, <tglx@...utronix.de>, <mingo@...hat.com>,
        <keescook@...omium.org>, <bhe@...hat.com>, <dyoung@...hat.com>,
        <arnd@...db.de>, <dave.jiang@...el.com>,
        <indou.takao@...fujitsu.com>, <izumi.taku@...fujitsu.com>,
        "Rafael J., Wysocki" <rjw@...ysocki.net>,
        "Zheng, Lv" <lv.zheng@...el.com>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Subject: Re: [POC] Get acpi table to limit memory scope chosen by KASLR to
 home SB when "movable_node" is specified

Cc ACPI maintainers and mail list

At 08/03/2017 04:51 PM, Chao Fan wrote:
> Hi all,
>
> Here is an issue about movable_node and KASLR.
> Currently, KASLR works well with "mem=", by which we can limit the scope of
> memory chosen by KASLR. But if we use "movable_node" independently without
> "mem=", we don't know the scope of memory in the home SB, which will cause
> the memory of hotplug SB may be chosen by KASLR.
> To solve this problem, I want to do this job:
> If "movable_node" is specified, try to get the acpi table and find the scope
> of memory in home SB, then set "mem_limit".
>
> The order of getting table is:
> boot_params
>     \-systab
>         \-efi tables
>              \-rsdp
>                  \-rsdt or xsdt
>                       \-acpi root table list
>                             \-acpi srat mem affinity
>
> I am not sure if it's OK for community.
> If there are any problems, please let me know.
> Any comments will be welcome.
>
> Thanks,
> Chao Fan
>
>
>


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ