From: Rob Landley <rob@landley.net>
To: Kees Cook <keescook@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
toybox@lists.landley.net, enh@google.com
Subject: Re: Regression: commit da029c11e6b1 broke toybox xargs.
Date: Sat, 4 Nov 2017 20:10:03 -0500 [thread overview]
Message-ID: <db7ed4a1-c6aa-6b21-ff2e-6c5b09e2fe30@landley.net> (raw)
In-Reply-To: <CAGXu5jK9OFZpvNeyKCit7gcSJQ=cR=KhHuv-LS3vf7AdxueA9Q@mail.gmail.com>
On 11/03/2017 08:37 PM, Kees Cook wrote:
> We don't. (In fact, arg copying happens before we've even figured out
> which binfmt is involved.) I lifted it to just before the point of no
> return, but moving it before arg copying looks very hard (which
> contributed to why we went with the implementation we did).
>
>> So it's pretty painful to make the limits different for suid and
>> non-suid binaries.
>
> I would agree.
I think I know what to implement for toybox now: xargs should trust
libc's sysconf() to provide the common-case starting limit (subtracting
env space) then implement the fallback pipe-from-child thing to
iteratively try half the argument list when that fails.
Elliott's even cc'd so he can update bionic's sysconf for the new 10 meg
thing from the title commit. :)
Rob
next prev parent reply other threads:[~2017-11-05 1:10 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 [this message]
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
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=db7ed4a1-c6aa-6b21-ff2e-6c5b09e2fe30@landley.net \
--to=rob@landley.net \
--cc=enh@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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.