| 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
| ||
|
Message-ID: <470BD539.9020703@zytor.com> Date: Tue, 09 Oct 2007 12:23:37 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: "Huang, Ying" <ying.huang@...el.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 -v4 0/3] i386/x86_64 boot: 32-bit boot protocol Huang, Ying wrote: > > - Which fields of boot parameters should be exported directly in > sysfs? Export all fields of boot parameters in sysfs is too complex > and unnecessary. Which fields should be? > The main this is that since this is a fixed-format, ABI-defined structure, regardless of individual fields it should be exported as a binary object. That is also the only way to deal with a kernel which may not itself know about specific items making the data available to other users, like kexec. It's not clear to me from reading the code what model you're using for exporting this data in sysfs. Could you describe it in some detail? What I had envisioned would be an object for the boot_params structure and a systematic object for each linked-list object, at a very minimum. -hpa - 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