public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nptl/26248] New: Incorrect argument types for INLINE_SETXID_SYSCALL Date: Thu, 16 Jul 2020 02:53:39 +0000 [thread overview] Message-ID: <bug-26248-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26248 Bug ID: 26248 Summary: Incorrect argument types for INLINE_SETXID_SYSCALL Product: glibc Version: 2.32 Status: NEW Severity: normal Priority: P2 Component: nptl Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com CC: drepper.fsp at gmail dot com Target Milestone: --- nptl has /* Opcodes and data types for communication with the signal handler to change user/group IDs. */ struct xid_command { int syscall_no; long int id[3]; volatile int cntr; volatile int error; /* -1: no call yet, 0: success seen, >0: error seen. */ }; /* This must be last, otherwise the current thread might not have permissions to send SIGSETXID syscall to the other threads. */ result = INTERNAL_SYSCALL_NCS (cmdp->syscall_no, 3, cmdp->id[0], cmdp->id[1], cmdp->id[2]); But arguments of some SETXID syscals are pointers: int setgroups(size_t size, const gid_t *list); which aren't handled properly. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-07-16 2:53 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-16 2:53 hjl.tools at gmail dot com [this message] 2020-07-16 8:24 ` [Bug nptl/26248] " fweimer at redhat dot com 2020-07-16 8:36 ` aurelien at aurel32 dot net 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@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).