linux-kernel - Re: [RFC/PATCH] RLIMIT_ARG

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]

Date:	Sat, 1 Mar 2008 08:42:21 +0000
From:	Geoff Clare <gwc@...ngroup.org>
To:	Michael Kerrisk <michael.kerrisk@...glemail.com>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	aaw <aaw@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>,
	carlos@...esourcery.com, Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>, drepper@...hat.com,
	mtk.manpages@...il.com
Subject: Re: [RFC/PATCH] RLIMIT_ARG_MAX

Michael Kerrisk <michael.kerrisk@...glemail.com> wrote, on 29 Feb 2008:
>
> My reading of POSIX.1 (and POSIX doesn't seem very explicit on this 
> point), is that the limits on argv+environ and on stack are decoupled, 
> since POSIX specifies RLIMIT_STACK and sysconf(_SC_ARG_MAX) and doesn't 
> specify any relationship between the two.

POSIX doesn't specify any relationship between them because (as far
as POSIX is concerned) they are limits on entirely different things.
sysconf(_SC_ARG_MAX) is a limit on how much arg+env a process can
_pass_ to the exec*() functions.  The RLIMIT_* limits are limits on
the process itself.

-- 
Geoff Clare <g.clare@...ngroup.org>
The Open Group, Thames Tower, Station Road, Reading, RG1 1LX, England
--
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/