From: Paolo Ornati <ornati@fastwebnet.it>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Benny Amorsen <benny+usenet@amorsen.dk>, linux-kernel@vger.kernel.org
Subject: Re: variable length argument support (was: [OT] Re: The vi editor causes brain damage)
Date: Sun, 19 Aug 2007 16:40:59 +0200 [thread overview]
Message-ID: <20070819164059.41b86c6b@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0708191505170.6042@fbirervta.pbzchgretzou.qr>
On Sun, 19 Aug 2007 15:07:01 +0200 (CEST)
Jan Engelhardt <jengelh@computergmbh.de> wrote:
> > Remove the arg+env limit of MAX_ARG_PAGES by copying the strings
> > directly from the old mm into the new mm.
>
> Me wonders. Will that make the "checking for maximum length of command line
> arguments" from autotools run forever since execve() will not fail anymore?
Since I'm running Gentoo and do many compiles I can tell that it
works :)
If I remeber correctly it was discussed on LKML and turend out that
that check is done starting with a "max" len and going down rather than
starting low and going up.
--
Paolo Ornati
Linux 2.6.23-rc3-g2a677896-dirty on x86_64
next prev parent reply other threads:[~2007-08-19 14:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 5:20 The vi editor causes brain damage Marc Perkel
2007-08-19 6:15 ` Al Viro
2007-08-19 6:29 ` Marc Perkel
2007-08-19 4:24 ` hotmetal
2007-08-19 13:07 ` Marc Perkel
2007-08-19 7:15 ` Jiri Slaby
2007-08-19 7:21 ` [OT] " Willy Tarreau
2007-08-19 12:31 ` Benny Amorsen
2007-08-19 12:39 ` Paolo Ornati
2007-08-19 13:07 ` variable length argument support (was: [OT] Re: The vi editor causes brain damage) Jan Engelhardt
2007-08-19 14:40 ` Paolo Ornati [this message]
2007-08-19 13:22 ` The vi editor causes brain damage Marc Perkel
2007-08-19 13:33 ` Willy Tarreau
2007-08-19 14:06 ` Jose Celestino
2007-08-19 14:48 ` Paolo Ornati
2007-08-19 15:32 ` Marc Perkel
2007-08-19 17:32 ` Arjan van de Ven
2007-08-19 23:03 ` Michael Tharp
2007-08-20 1:55 ` Casey Dahlin
2007-08-19 13:55 ` [OT] " Torsten Duwe
2007-08-19 13:08 ` Marc Perkel
2007-08-19 20:14 ` Valdis.Kletnieks
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=20070819164059.41b86c6b@localhost \
--to=ornati@fastwebnet.it \
--cc=benny+usenet@amorsen.dk \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.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 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.