linux-kernel - Re: Regression: commit da029c11e6b1 broke toybox xargs.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 15 Nov 2017 14:45:44 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     enh <enh@...gle.com>
Cc:     Rob Landley <rob@...dley.net>, Kees Cook <keescook@...omium.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        toybox@...ts.landley.net
Subject: Re: Regression: commit da029c11e6b1 broke toybox xargs.

On Wed, Nov 15, 2017 at 2:10 PM, enh <enh@...gle.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