From: "H. Peter Anvin" <hpa@zytor.com>
To: David Cullen <David.Cullen@koe-americas.com>
Cc: Michal Marek <mmarek@suse.cz>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] Fix "/usr/bin/xargs: rm: Argument list too long" during make distclean
Date: Mon, 13 Aug 2012 14:01:40 -0700 [thread overview]
Message-ID: <50296B34.8090502@zytor.com> (raw)
In-Reply-To: <502969FA.6010907@koe-americas.com>
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
next prev parent reply other threads:[~2012-08-13 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 19:39 [PATCH RFC] Fix "/usr/bin/xargs: rm: Argument list too long" during make distclean David Cullen
2012-08-13 20:38 ` H. Peter Anvin
2012-08-13 20:56 ` David Cullen
2012-08-13 20:56 ` David Cullen
2012-08-13 21:01 ` H. Peter Anvin [this message]
2012-08-14 12:54 ` David Cullen
2012-08-14 12:54 ` David Cullen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50296B34.8090502@zytor.com \
--to=hpa@zytor.com \
--cc=David.Cullen@koe-americas.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.