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/31479] New: Missing #include <sys/rseq.h> in sched_getcpu.c may result in a loss of rseq acceleration Date: Wed, 13 Mar 2024 10:28:30 +0000 [thread overview] Message-ID: <bug-31479-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31479 Bug ID: 31479 Summary: Missing #include <sys/rseq.h> in sched_getcpu.c may result in a loss of rseq acceleration Product: glibc Version: 2.35 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: --- This commit removed #include <sys/rseq.h> from nptl/descr.h: commit 2c6b4b272e6b4d07303af25709051c3e96288f2d Author: Florian Weimer <fweimer@redhat.com> Date: Fri Jul 21 16:18:18 2023 +0200 nptl: Unconditionally use a 32-byte rseq area If the kernel headers provide a larger struct rseq, we used that size as the argument to the rseq system call. As a result, rseq registration would fail on older kernels which only accept size 32. As a result, <sys/rseq.h> may or may not be implicitly included when sysdeps/unix/sysv/linux/sched_getcpu.c is built. If <sys/rseq.h> is not included, RSEQ_SIG is not defined, and we do not get rseq acceleration even if supported on the architecture. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-03-13 10:28 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-13 10:28 fweimer at redhat dot com [this message] 2024-03-13 10:28 ` [Bug libc/31479] " fweimer at redhat dot com 2024-03-13 12:24 ` fweimer at redhat dot com 2024-03-18 11:31 ` fweimer at redhat dot com 2024-03-18 11:32 ` 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-31479-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).