From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Changqing Li <changqing.li@windriver.com>,
Namhyung Kim <namhyung@google.com>,
namhyung@kernel.org, james.clark@linaro.org,
charlie@rivosinc.com, linux-kernel@vger.kernel.org,
Markus Mayer <mmayer@broadcom.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH] tools/build: make in-target rule robust against too long argument error
Date: Wed, 4 Mar 2026 11:13:28 -0300 [thread overview]
Message-ID: <aag-CNeYM8q4HskX@x1> (raw)
In-Reply-To: <CAP-5=fUCyYVg-h=YuLy9HRDWzvc7Jm3a9tZM29Bez4R-eTBSOQ@mail.gmail.com>
On Tue, Mar 03, 2026 at 02:33:04PM -0800, Ian Rogers wrote:
> On Mon, Oct 27, 2025 at 7:16 PM Changqing Li <changqing.li@windriver.com> wrote:
> > Kindly ping. Could you reproduce it? Any comments?
> Sorry Changqing,
> I was reminded by:
> https://lore.kernel.org/lkml/20260303211503.165337-1-mmayer@broadcom.com/
> that "argument list too long" is a problem for others.
> I tried reproducing it, but I think it doesn't fail for me, possibly
> because MAX_ARGS is larger on my system:
> ```
> $ xargs --show-limits
> Your environment variables take up 6133 bytes
> POSIX upper limit on argument length (this system): 2088971
> POSIX smallest allowable upper limit on argument length (all systems): 4096
> Maximum length of command we could actually use: 2082838
> Size of command buffer we are actually using: 131072
> Maximum parallelism (--max-procs must be no greater): 2147483647
> ```
> Anyway, the change makes sense to me.
> Reviewed-by: Ian Rogers <irogers@google.com>
Ok, so I'll pick this one and the other for rm that you mentioned:
https://lore.kernel.org/lkml/20260303211503.165337-1-mmayer@broadcom.com
I'll have it in perf-tools, for v7.0.
- Arnaldo
prev parent reply other threads:[~2026-03-04 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250728093153.2330009-1-changqing.li@windriver.com>
[not found] ` <CAP-5=fW983q0NUEvxibY+QKLss+_TsyRGtgZF_n_q-XFZ98JLA@mail.gmail.com>
[not found] ` <ef286bfd-0703-4393-87eb-4b0a85084767@windriver.com>
[not found] ` <00dac1a5-16b0-4b54-8525-c0c706f08626@windriver.com>
2026-03-03 22:33 ` [PATCH] tools/build: make in-target rule robust against too long argument error Ian Rogers
2026-03-04 2:35 ` Changqing Li
2026-03-04 14:13 ` Arnaldo Carvalho de Melo [this message]
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=aag-CNeYM8q4HskX@x1 \
--to=acme@kernel.org \
--cc=changqing.li@windriver.com \
--cc=charlie@rivosinc.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mmayer@broadcom.com \
--cc=namhyung@google.com \
--cc=namhyung@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox