public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sdrake at xnet dot co.nz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13280] New: execve(2) does not honor sysconf(_SC_ARG_MAX) in some cases. Date: Tue, 11 Oct 2011 08:36:00 -0000 [thread overview] Message-ID: <bug-13280-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13280 Bug #: 13280 Summary: execve(2) does not honor sysconf(_SC_ARG_MAX) in some cases. Product: glibc Version: 2.13 Status: NEW Severity: critical Priority: P2 Component: libc AssignedTo: drepper.fsp@gmail.com ReportedBy: sdrake@xnet.co.nz Classification: Unclassified Host: x86_64-unknown-linux-gnu Steven Drake <sdrake at xnet dot co.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |testsuite+ Created attachment 5974 --> http://sourceware.org/bugzilla/attachment.cgi?id=5974 test-skeleton.c based test case (causes execve to fail with E2BIG). If execve is given an argv with a string that is larger than 131072 (coincidentally the ARG_MAX macro from linux/limits.h) but less than what sysconf(_SC_ARG_MAX) return, execve fails with E2BIG. This does not happen if the total length of the argv strings is greater than ARG_MAX but each is shorter. This is a problem if using "/bin/sh -c", i.e. system(3). I'm not sure if this is a glibc or linux issue but I am reporting it here anyway. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-10-11 8:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-11 8:36 sdrake at xnet dot co.nz [this message] 2011-10-11 8:52 ` [Bug libc/13280] " schwab@linux-m68k.org 2012-03-08 4:24 ` carlos at systemhalted dot org 2014-06-13 10:43 ` fweimer at redhat dot com
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=bug-13280-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).