public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29771] New: Restore IPC_64 support in sysvipc *ctl functions Date: Thu, 10 Nov 2022 10:36:34 +0000 [thread overview] Message-ID: <bug-29771-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29771 Bug ID: 29771 Summary: Restore IPC_64 support in sysvipc *ctl functions Product: glibc Version: 2.37 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: fweimer at redhat dot com CC: drepper.fsp at gmail dot com Target Milestone: --- Flags: security- In order to call SHM_STAT_ANY kernel operations through shmctl on older glibc, it was necessary to pass SHM_STAT_ANY | IPC_64 in the command argument, otherwise the ipc system call would be invoked without the IPC_64 flag, giving unexpected results on powerpc64le-linux-gnu at least. Current glibc no longer supports that because it checks the command argument for validity without masking the IPC_64 bit. Patch posted: [PATCH] Linux: Support __IPC_64 in sysvctl *ctl command arguments <https://sourceware.org/pipermail/libc-alpha/2022-November/143343.html> -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-11-10 10:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-10 10:36 fweimer at redhat dot com [this message] 2022-11-10 10:36 ` [Bug libc/29771] " fweimer at redhat dot com 2022-11-10 10:37 ` fweimer at redhat dot com 2022-11-10 10:54 ` fweimer at redhat dot com 2022-11-10 13:23 ` fweimer at redhat dot com 2022-11-11 18:16 ` 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-29771-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).