| 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
| ||
|
Date: Thu, 03 Aug 2006 17:59:49 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Adrian Bunk <bunk@...sta.de> CC: Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org, David Woodhouse <dwmw2@...radead.org> Subject: Re: Userspace visible of 3 include/asm/ headers Adrian Bunk wrote: > On Thu, Aug 03, 2006 at 04:51:38PM -0700, H. Peter Anvin wrote: >> Adrian Bunk wrote: >> >>> On different architectures, we have the following values for >>> COMMAND_LINE_SIZE: >>> - 256 >>> - 512 >>> - 896 >>> - 1024 >>> - 4096 >>> >>> What should be the common value? >>> 4096? >>> >>> And I have a rough memory of some dependencies of COMMAND_LINE_SIZE and >>> boot loaders. What exactly must be taken care of when increasing >>> COMMAND_LINE_SIZE? >>> >> It's architecture-dependent; it probably should be defined in something >> like <asm/cmdline.h>. > > OK, I did misunderstand you. > I tought you were saying it should be the same value for all > architectures. > > With the exception of frv (in param.h), COMMAND_LINE_SIZE is in setup.h > on all architectures. > > Do we want to move it to a different header, or simply make param.h a > userspace header on all architectures? > I figure it should be broken out into a separate header, rather than exporting all of setup.h. -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