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: <1190873200.21818.292.camel@caritas-dev.intel.com>
Date:	Thu, 27 Sep 2007 14:06:40 +0800
From:	"Huang, Ying" <ying.huang@...el.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Andi Kleen <ak@...e.de>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	akpm@...ux-foundation.org, Yinghai Lu <yhlu.kernel@...il.com>,
	Chandramouli Narayanan <mouli@...ux.intel.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm -v3 1/2] i386/x86_64 boot: setup data

Hi, Peter,

On Wed, 2007-09-19 at 09:04 -0700, H. Peter Anvin wrote:
> Huang, Ying wrote:
> > 
> > Known Issues:
> > 
> > 1. Where is safe to place the linked list of setup_data?
> > Because the length of the linked list of setup_data is variable, it
> > can not be copied into BSS segment of kernel as that of "zero
> > page". We must find a safe place for it, where it will not be
> > overwritten by kernel during booting up. The i386 kernel will
> > overwrite some pages after _end. The x86_64 kernel will overwrite some
> > pages from 0x1000 on.
> > 
> 
> The latter is definitely not safe, since the space below 640K is the
> documented place to put the command line (and presumably where the
> bootloader would put other auxilliary chunks.)
> 
> I'll try to do a full review of this later today.  Haven't had time yet
> to look at this anything than but piecemeal.

Do you think this patch and the 32-bit boot protocol patch are ready to
merge for -mm? If not, I can revise them.

Best Regards,
Huang Ying
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ