linux-kernel - Re: execve manpage changes

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: <46B8E05C.8080405@gmx.net>
Date:	Tue, 07 Aug 2007 23:13:00 +0200
From:	Michael Kerrisk <mtk-manpages@....net>
To:	Ollie Wild <aaw@...gle.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: execve manpage changes

Ollie Wild wrote:
> Michael,
> 
> Per our previous discussion, here are the updates to the execve(2)
> manpage resulting from the variable length argument support patch in
> linux-2.6.23-rc1.  The execve API is unmodified.  However, the
> following should be noted in the "Notes" section.
> 
> Prior to linux-2.6.23, the memory used to store the environment and
> argument list strings was limited to 32 (MAX_ARG_PAGES) pages.  On
> most architectures, the page size is 4kB, leading to a maximum size of
> 128kB.
> 
> In linux-2.6.23 and later, most architectures support a size limit
> derived from the current RLIMIT_STACK setting (see getrlimit(2)).  For
> these architectures, the total size is limited to 1/4 the allowed
> stack size, the limit per string is 32 pages (MAX_ARG_STRLEN), and the
> maximum number of strings is 0x7FFFFFFF.  Architectures with no memory
> management unit are excepted: they maintain the pre-2.6.23 limit.

Hello Ollie,

Thanks.  I'll see that this material makes it into a man pages release 
closer to the 2.6.23 final release.

Cheers,

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