linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: "'alexs@kernel.org'" <alexs@kernel.org>,
	Eric Biederman <ebiederm@xmission.com>,
	Kees Cook <keescook@chromium.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Alex Shi <alexsshi@tencent.com>,
	"curlinhuang@tencent.com" <curlinhuang@tencent.com>
Subject: RE: [PATCH] execve: argument list space enlargement
Date: Fri, 5 Jan 2024 12:02:08 +0000	[thread overview]
Message-ID: <1834358b1a8642f9b46a209bad035474@AcuMS.aculab.com> (raw)
In-Reply-To: <20240103130722.1551670-1-alexs@kernel.org>

From: alexs@kernel.org
> Sent: 03 January 2024 13:07
> 
> From: Alex Shi <alexsshi@tencent.com>
> 
> Wechat using too long gcc parameters, then get a strace complain:
>   execve(...) = -1 E2BIG (Argument list too long)
> Have to increase the parameter space for this, stack has enough
> space for this enlargement.

They should fix their build so that it doesn't explode.
It'll probably speed up the compiles as well since the
very long argv[] almost certainly comes from a lot of -I dir
options and they slow down the compile.

if they are -Dvar[=val] then '-include file' can be used instead.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)



  reply	other threads:[~2024-01-05 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 13:07 alexs
2024-01-05 12:02 ` David Laight [this message]
2024-01-11  0:13 ` Kees Cook

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=1834358b1a8642f9b46a209bad035474@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=alexs@kernel.org \
    --cc=alexsshi@tencent.com \
    --cc=curlinhuang@tencent.com \
    --cc=ebiederm@xmission.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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