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: <50296B34.8090502@zytor.com>
Date:	Mon, 13 Aug 2012 14:01:40 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	David Cullen <David.Cullen@...-americas.com>
CC:	Michal Marek <mmarek@...e.cz>,
	"linux-kbuild@...r.kernel.org" <linux-kbuild@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC] Fix "/usr/bin/xargs: rm: Argument list too long"
 during make distclean

On 08/13/2012 01:56 PM, David Cullen wrote:
>>
>> That sounds like a bug in xargs...
>>
> 
> In my specific case, qemu-arm-static calls xargs (In fact, in my
> cross chroot, qemu-arm-static is used to run every user mode process).
> 
> Do you mean that qemu-arm-static is exposing a latent defect in xargs?
> 
> Does qemu-arm-static steal some of the command line space that would
> normally be available for xargs? If so, how would xargs figure out
> this was happening and handle the problem?
> 

I have no idea.  Perhaps strace can help you see what is happening, I
don't know.  More likely it is qemu-arm-static that is broken and it is
trying to enforce the old 128K limit that we used to have before 2.6.23.
 This could cause a mismatch between what sysconf(_SC_ARG_MAX) returns
and what the actual limit is.

Anyway, even more so the reason to reject this patch.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ