linux-kernel - Re: [PATCH] Prevent reserving RAM in the region already reserved by BIOS

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:	Wed, 19 May 2010 10:40:38 -0700
From:	Yinghai <yinghai.lu@...cle.com>
To:	Mathieu Rondonneau <mathieu.rondonneau@...il.com>
CC:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] Prevent reserving RAM in the region already reserved
 by BIOS

On 05/18/2010 10:35 PM, Mathieu Rondonneau wrote:
> Does it make sense to prevent looking for stolen RAM below the ISA section.
> 
> 
> Signed-off-by: Mathieu Rondonneau <mathieu.rondonneau@...il.com>
> ---
>  arch/x86/kernel/e820.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
> index 7bca3c6..322c9c3 100644
> --- a/arch/x86/kernel/e820.c
> +++ b/arch/x86/kernel/e820.c
> @@ -1156,6 +1156,8 @@ void __init e820_reserve_resources_late(void)
>                         end = MAX_RESOURCE_SIZE;
>                 if (start >= end)
>                         continue;
> +               if (end < ISA_START_ADDRESS)
> +                       continue;
>                 printk(KERN_DEBUG "reserve RAM buffer: %016llx - %016llx ",
>                                start, end);
>                 reserve_region_with_split(&iomem_resource, start, end,

do you notice any changes in /proc/iomem?

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/