linux-kernel - Re: [PATCH -mm -v5 0/3] i386/x86

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: <m1abqif5dp.fsf@ebiederm.dsl.xmission.com>
Date:	Wed, 17 Oct 2007 03:38:10 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	"Huang, Ying" <ying.huang@...el.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Andi Kleen <ak@...e.de>,
	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 -v5 0/3] i386/x86_64 boot: 32-bit boot protocol

"Huang, Ying" <ying.huang@...el.com> writes:

> This patchset defines a 32-bit boot protocol for i386/x86_64 platform,
> adds an extensible boot parameter passing mechanism, export the boot
> parameters via sysfs.
>
> The patchset has been tested against 2.6.23-rc8-mm2 kernel on x86_64
> and i386.
>
> This patchset is based on the proposal of Peter Anvin.
>
>
> Known Issues:
>
> - 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.

Well there actually is no reason to copy the current data into the
zero page.  We really should just leave it where it is until the
kernel has managed to bootstrap it's basic services.

As for the setup data can we please remove the pointers. And just
require the that the data items be appended one after each other
in memory.  Then we would just need a field where we could
report an offset to the binary data from where we loaded the
16bit code/data.  We could even specify the end by requiring
that we fill in setup_move_size or something of that nature.

Beyond that we should provide the bootloaders enough information to
know which information the kernel will overwrite before it consults
the e820 map and other indicators of what memory is free.

Eric
-
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/