linux-kernel - Re: Userspace visible of 3 include/asm/ headers

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: <44D28C0A.905@zytor.com>
Date:	Thu, 03 Aug 2006 16:51:38 -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 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>.

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