linux-kernel - Re: variable length argument support (was: [OT] Re: The vi editor causes brain damage)

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:	Sun, 19 Aug 2007 15:07:01 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Paolo Ornati <ornati@...twebnet.it>
cc:	Benny Amorsen <benny+usenet@...rsen.dk>,
	linux-kernel@...r.kernel.org
Subject: Re: variable length argument support (was: [OT] Re: The vi editor
 causes brain damage)


On Aug 19 2007 14:39, Paolo Ornati wrote:
>> WT> Under unix, the shell resolves "*" and passes the 10000 file names
>> WT> to the "rm" command. Now, execve() may fail because 10000 names in
>> WT> arguments can require too much memory. That's why find and xargs
>> WT> were invented!
>> 
>> It would be very handy if the argument memory space was expanded.
>> Many years ago I hit the limit regularly on Solaris, and going to
>> Linux with its comparatively large limit was a joy. Now it happens to
>> me quite often on Linux as well.
>> 
>
>done  :)
>
>commit b6a2fea39318e43fee84fa7b0b90d68bed92d2ba
>Author: Ollie Wild <aaw@...gle.com>
>Date:   Thu Jul 19 01:48:16 2007 -0700
>
>    mm: variable length argument support
>
>    Remove the arg+env limit of MAX_ARG_PAGES by copying the strings
>    directly from the old mm into the new mm.

Me wonders. Will that make the "checking for maximum length of command line
arguments" from autotools run forever since execve() will not fail anymore?



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