public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nptl/26248] Incorrect argument types for INLINE_SETXID_SYSCALL Date: Thu, 16 Jul 2020 08:36:11 +0000 [thread overview] Message-ID: <bug-26248-131-YMWTiZ4Oui@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26248-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26248 Aurelien Jarno <aurelien at aurel32 dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aurelien at aurel32 dot net --- Comment #2 from Aurelien Jarno <aurelien at aurel32 dot net> --- Created attachment 12703 --> https://sourceware.org/bugzilla/attachment.cgi?id=12703&action=edit Reproducer for the issue Please find attached a small reproducer for the issue. Compile it with "gcc -mx32 -o setgroups-x32 setgroups-x32.c -lpthread". Running it as root returns: # ./setgroups-x32 setgroups failed: Bad address It runs successfully with commit df76ff3a446a787a95cf74cb15c285464d73a93d reverted. (Note that this commit has been backported in 2.30 and 2.31). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-07-16 8:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-16 2:53 [Bug nptl/26248] New: " hjl.tools at gmail dot com 2020-07-16 8:24 ` [Bug nptl/26248] " fweimer at redhat dot com 2020-07-16 8:36 ` aurelien at aurel32 dot net [this message] 2020-07-16 8:37 ` aurelien at aurel32 dot net 2020-07-16 11:29 ` hjl.tools at gmail dot com 2020-08-18 10:04 ` schwab@linux-m68k.org 2020-08-18 13:04 ` carlos 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-26248-131-YMWTiZ4Oui@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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).