linux-kernel - Re: [BUG] Linux 2.6.23-rc9 and MAX_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:	Thu, 4 Oct 2007 10:27:52 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Mathieu Chouquet-Stringer <mchouque@...e.fr>
cc:	Ollie Wild <aaw@...gle.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Adrian Bunk <bunk@...sta.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [BUG] Linux 2.6.23-rc9 and MAX_ARG_PAGES

On Thu, 4 Oct 2007, Mathieu Chouquet-Stringer wrote:
> 
> I've seen the changes you made in commit b6a2fea39318 and I guess they
> might be responsible for my xargs breakage...
> 
> In the kernel source tree, if I run a stupid find | xargs ls, I now get
> this:
> xargs: ls: Argument list too long

What does your "ulimit -s" say?

I suspect that you might hit the code that limits execve() arguments to 
one quarter of the maximum stack size.

We could change that from 25% to something else (half? three quarters?), 
but if you really are hitting that limit, it sounds like you may have a 
really small stack size to begin with (ie if 25% is smaller than the old 
argument size limit of 128kB, you're running with a stack limit of less 
than half a meg, which sounds pretty dang small).

So I'd like to verify that the stack limit really is the issue, and not 
something else.

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