public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/25305] wrong _SC_ARG_MAX from sysconf
       [not found] <bug-25305-131@http.sourceware.org/bugzilla/>
@ 2021-04-13 20:12 ` cvs-commit at gcc dot gnu.org
  2021-04-13 20:14 ` adhemerval.zanella at linaro dot org
  1 sibling, 0 replies; 2+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2021-04-13 20:12 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=25305

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Adhemerval Zanella
<azanella@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=a9880586eedb3ba89ca6a7c5e3f0664c279cf636

commit a9880586eedb3ba89ca6a7c5e3f0664c279cf636
Author: Michal Nazarewicz <mina86@mina86.com>
Date:   Wed Apr 7 17:10:58 2021 +0200

    linux: sysconf: limit _SC_MAX_ARG to 6 MiB (BZ #25305)

    Since Linux 4.13, kernel limits the maximum command line arguments
    length to 6 MiB [1].  Normally the limit is still quarter of the maximum
    stack size but if that limit exceeds 6 MiB it's clamped down.

    glibc's __sysconf implementation for Linux platform is not aware of
    this limitation and for stack sizes of over 24 MiB it returns higher
    ARG_MAX than Linux will actually accept.  This can be verified by
    executing the following application on Linux 4.13 or newer:

        #include <stdio.h>
        #include <string.h>
        #include <sys/resource.h>
        #include <sys/time.h>
        #include <unistd.h>

        int main(void) {
                const struct rlimit rlim = { 40 * 1024 * 1024,
                                             40 * 1024 * 1024 };
                if (setrlimit(RLIMIT_STACK, &rlim) < 0) {
                        perror("setrlimit: RLIMIT_STACK");
                        return 1;
                }

                printf("ARG_MAX     : %8ld\n", sysconf(_SC_ARG_MAX));
                printf("63 * 100 KiB: %8ld\n", 63L * 100 * 1024);
                printf("6 MiB       : %8ld\n", 6L * 1024 * 1024);

                char str[100 * 1024], *argv[64], *envp[1];
                memset(&str, 'A', sizeof str);
                str[sizeof str - 1] = '\0';
                for (size_t i = 0; i < sizeof argv / sizeof *argv - 1; ++i) {
                        argv[i] = str;
                }
                argv[sizeof argv / sizeof *argv - 1] = envp[0] = 0;

                execve("/bin/true", argv, envp);
                perror("execve");
                return 1;
        }

    On affected systems the program will report ARG_MAX as 10 MiB but
    despite that executing /bin/true with a bit over 6 MiB of command line
    arguments will fail with E2BIG error.  Expected result is that ARG_MAX
    is reported as 6 MiB.

    Update the __sysconf function to clamp ARG_MAX value to 6 MiB if it
    would otherwise exceed it.  This resolves bug #25305 which was market
    WONTFIX as suggested solution was to cap ARG_MAX at 128 KiB.

    As an aside and point of comparison, bionic (a libc implementation for
    Android systems) decided to resolve this issue by always returning 128
    KiB ignoring any potential xargs regressions [2].

    On older kernels this results in returning overly conservative value
    but that's a safer option than being aggressive and returning invalid
    value on recent systems.  It's also worth noting that at this point
    all supported Linux releases have the 6 MiB barrier so only someone
    running an unsupported kernel version would get incorrectly truncated
    result.

    Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

    [1] See
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=da029c11e6b12f321f36dac8771e833b65cec962
    [2] See
https://android.googlesource.com/platform/bionic/+/baed51ee3a13dae4b87b11870bdf7f10bdc9efc1

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug libc/25305] wrong _SC_ARG_MAX from sysconf
       [not found] <bug-25305-131@http.sourceware.org/bugzilla/>
  2021-04-13 20:12 ` [Bug libc/25305] wrong _SC_ARG_MAX from sysconf cvs-commit at gcc dot gnu.org
@ 2021-04-13 20:14 ` adhemerval.zanella at linaro dot org
  1 sibling, 0 replies; 2+ messages in thread
From: adhemerval.zanella at linaro dot org @ 2021-04-13 20:14 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=25305

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WONTFIX                     |FIXED
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg

--- Comment #4 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
Fixed on 2.34.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-04-13 20:14 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-25305-131@http.sourceware.org/bugzilla/>
2021-04-13 20:12 ` [Bug libc/25305] wrong _SC_ARG_MAX from sysconf cvs-commit at gcc dot gnu.org
2021-04-13 20:14 ` adhemerval.zanella at linaro dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).