From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Ingo Molnar <mingo@kernel.org>, Thomas Gleixner <tglx@kernel.org>,
Carlos O'Donell <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
Michael Jeanson <mjeanson@efficios.com>
Subject: [PATCH v1 0/2] Last minute rseq fixes for 7.0
Date: Wed, 18 Feb 2026 11:52:12 -0500 [thread overview]
Message-ID: <20260218165214.1164084-1-mathieu.desnoyers@efficios.com> (raw)
Hi,
Here are two last minute rseq fixes aiming at 7.0.
The first is a clarification of a rseq registration comment to match the
rseq_size range checks.
The second ensures that the new scheduler slice extension field don't
end up exposing a rseq feature size equal to the original rseq size,
which would make life harder than it needs to be for userspace.
Thanks,
Mathieu
CC: Peter Zijlstra (Intel) <peterz@infradead.org>
CC: Ingo Molnar <mingo@kernel.org>
CC: Thomas Gleixner <tglx@kernel.org>
CC: Carlos O'Donell <carlos@redhat.com>
CC: Florian Weimer <fweimer@redhat.com>
CC: Michael Jeanson <mjeanson@efficios.com>
Mathieu Desnoyers (2):
rseq: Clarify rseq registration rseq_size bound check comment
rseq: slice ext: Ensure rseq feature size differs from original rseq
size
include/uapi/linux/rseq.h | 13 ++++++++++++-
kernel/rseq.c | 5 +++--
2 files changed, 15 insertions(+), 3 deletions(-)
--
2.39.5
next reply other threads:[~2026-02-18 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 16:52 Mathieu Desnoyers [this message]
2026-02-18 16:52 ` [PATCH v1 1/2] rseq: Clarify rseq registration rseq_size bound check comment Mathieu Desnoyers
2026-02-18 16:52 ` [PATCH v1 2/2] rseq: slice ext: Ensure rseq feature size differs from original rseq size Mathieu Desnoyers
2026-02-18 19:01 ` Mathieu Desnoyers
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=20260218165214.1164084-1-mathieu.desnoyers@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mjeanson@efficios.com \
--cc=peterz@infradead.org \
--cc=tglx@kernel.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: link
Be 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
all inboxes | Powered by JetHome®