All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: enh <enh@google.com>
Cc: Rob Landley <rob@landley.net>, Kees Cook <keescook@chromium.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	toybox@lists.landley.net
Subject: Re: Regression: commit da029c11e6b1 broke toybox xargs.
Date: Wed, 15 Nov 2017 14:45:44 -0800	[thread overview]
Message-ID: <CA+55aFwk_gP=62YCe-wL5WWYt9h3YWaH-rQmQp-OWHCX3jQKeQ@mail.gmail.com> (raw)
In-Reply-To: <CAJgzZopVb5CC-T6GTYTAGKwY+vQ9Muvi3g6jKNmOC1+4BTMNvQ@mail.gmail.com>

On Wed, Nov 15, 2017 at 2:10 PM, enh <enh@google.com> wrote:
>>
>> I actually suspect "just use 128kB" is the actual best option in practice.
>
> for libc's sysconf(_SC_ARG_MAX) too? i'm fine changing bionic back to
> reporting 128KiB if there's an lkml "Linus says" mail that i can link
> to in the comment. it certainly seems like an overly-conservative
> choice is better than the current situation...

I suspect a 128kB sysconf(_SC_ARG_MAX) is the sanest bet, simply
because of that "conservative is better than aggressive".

Especially since _technically_ we're still limiting things to that
128kB due to the single-string limit.

              Linus

  reply	other threads:[~2017-11-15 22:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 23:34 Regression: commit da029c11e6b1 broke toybox xargs Rob Landley
2017-11-02  3:30 ` Kees Cook
     [not found] ` <CA+55aFyw74DcPygS=SB0d-Fufz3j73zTVp2UXUUOUt4=1_He=Q@mail.gmail.com>
2017-11-02 15:40   ` Linus Torvalds
2017-11-03 23:58     ` Rob Landley
2017-11-04  0:03       ` [Toybox] " enh
2017-11-04  0:42       ` Kees Cook
2017-11-04  1:22         ` Linus Torvalds
2017-11-04  1:37           ` Kees Cook
2017-11-05  1:10             ` Rob Landley
2017-11-04  1:07       ` Linus Torvalds
2017-11-05  0:39         ` Rob Landley
2017-11-05 20:46           ` Linus Torvalds
2017-11-15 22:10             ` enh
2017-11-15 22:45               ` Linus Torvalds [this message]
2017-11-15 21:12           ` Pavel Machek

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='CA+55aFwk_gP=62YCe-wL5WWYt9h3YWaH-rQmQp-OWHCX3jQKeQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=enh@google.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=toybox@lists.landley.net \
    /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.