From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Cc: Michael Jeanson <mjeanson@efficios.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>, Wei Liu <wei.liu@kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [patch 01/11] rseq: Avoid pointless evaluation in __rseq_notify_resume()
Date: Wed, 20 Aug 2025 10:23:36 -0400 [thread overview]
Message-ID: <8fdb9b21-a918-44bb-b9a0-cd8cbe6379c7@efficios.com> (raw)
In-Reply-To: <20250813162823.845026450@linutronix.de>
On 2025-08-13 12:29, Thomas Gleixner wrote:
> The RSEQ critical section mechanism only clears the event mask when a
> critical section is registered, otherwise it is stale and collects
> bits.
>
> That means once a critical section is installed the first invocation of
> that code when TIF_NOTIFY_RESUME is set will abort the critical section,
> even when the TIF bit was not raised by the rseq preempt/migrate/signal
> helpers.
>
> This also has a performance implication because TIF_NOTIFY_RESUME is a
> multiplexing TIF bit, which is utilized by quite some infrastructure. That
> means every invocation of __rseq_notify_resume() goes unconditionally
> through the heavy lifting of user space access and consistency checks even
> if there is no reason to do so.
>
> Keeping the stale event mask around when exiting to user space also
> prevents it from being utilized by the upcoming time slice extension
> mechanism.
>
> Avoid this by reading and clearing the event mask before doing the user
> space critical section access with preemption disabled, which ensures that
> the read and clear operation is CPU local atomic versus scheduling.
>
> This is correct as after re-enabling preemption any relevant event will set
> the bit again and raise TIF_NOTIFY_RESUME, which makes the user space exit
> code take another round of TIF bit clearing.
>
> If the event mask was non-zero, invoke the slow path. On debug kernels the
> slow path is invoked unconditionally and the result of the event mask
> evaluation is handed in.
>
> Add a exit path check after the TIF bit loop, which validates on debug
> kernels that the event mask is zero before exiting to user space.
>
> While at it reword the convoluted comment why the pt_regs pointer can be
> NULL under certain circumstances.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: "Paul E. McKenney" <paulmck@kernel.org>
> Cc: Boqun Feng <boqun.feng@gmail.com>
> ---
> include/linux/irq-entry-common.h | 7 ++--
> include/linux/rseq.h | 10 +++++
> kernel/rseq.c | 66 ++++++++++++++++++++++++++-------------
> 3 files changed, 58 insertions(+), 25 deletions(-)
>
> --- a/include/linux/irq-entry-common.h
> +++ b/include/linux/irq-entry-common.h
> @@ -2,11 +2,12 @@
> #ifndef __LINUX_IRQENTRYCOMMON_H
> #define __LINUX_IRQENTRYCOMMON_H
>
> +#include <linux/context_tracking.h>
> +#include <linux/kmsan.h>
> +#include <linux/rseq.h>
> #include <linux/static_call_types.h>
> #include <linux/syscalls.h>
> -#include <linux/context_tracking.h>
> #include <linux/tick.h>
> -#include <linux/kmsan.h>
> #include <linux/unwind_deferred.h>
>
> #include <asm/entry-common.h>
> @@ -226,6 +227,8 @@ static __always_inline void exit_to_user
>
> arch_exit_to_user_mode_prepare(regs, ti_work);
>
> + rseq_exit_to_user_mode();
> +
> /* Ensure that kernel state is sane for a return to userspace */
> kmap_assert_nomap();
> lockdep_assert_irqs_disabled();
> --- a/include/linux/rseq.h
> +++ b/include/linux/rseq.h
> @@ -66,6 +66,14 @@ static inline void rseq_migrate(struct t
> rseq_set_notify_resume(t);
> }
>
> +static __always_inline void rseq_exit_to_user_mode(void)
> +{
> + if (IS_ENABLED(CONFIG_DEBUG_RSEQ)) {
> + if (WARN_ON_ONCE(current->rseq && current->rseq_event_mask))
> + current->rseq_event_mask = 0;
> + }
> +}
> +
> /*
> * If parent process has a registered restartable sequences area, the
> * child inherits. Unregister rseq for a clone with CLONE_VM set.
> @@ -118,7 +126,7 @@ static inline void rseq_fork(struct task
> static inline void rseq_execve(struct task_struct *t)
> {
> }
> -
> +static inline void rseq_exit_to_user_mode(void) { }
> #endif
>
> #ifdef CONFIG_DEBUG_RSEQ
> --- a/kernel/rseq.c
> +++ b/kernel/rseq.c
> @@ -324,9 +324,9 @@ static bool rseq_warn_flags(const char *
> return true;
> }
>
> -static int rseq_need_restart(struct task_struct *t, u32 cs_flags)
> +static int rseq_check_flags(struct task_struct *t, u32 cs_flags)
> {
> - u32 flags, event_mask;
> + u32 flags;
> int ret;
>
> if (rseq_warn_flags("rseq_cs", cs_flags))
> @@ -339,17 +339,7 @@ static int rseq_need_restart(struct task
>
> if (rseq_warn_flags("rseq", flags))
> return -EINVAL;
> -
> - /*
> - * Load and clear event mask atomically with respect to
> - * scheduler preemption and membarrier IPIs.
> - */
> - scoped_guard(RSEQ_EVENT_GUARD) {
> - event_mask = t->rseq_event_mask;
> - t->rseq_event_mask = 0;
> - }
> -
> - return !!event_mask;
> + return 0;
> }
>
> static int clear_rseq_cs(struct rseq __user *rseq)
> @@ -380,7 +370,7 @@ static bool in_rseq_cs(unsigned long ip,
> return ip - rseq_cs->start_ip < rseq_cs->post_commit_offset;
> }
>
> -static int rseq_ip_fixup(struct pt_regs *regs)
> +static int rseq_ip_fixup(struct pt_regs *regs, bool abort)
> {
> unsigned long ip = instruction_pointer(regs);
> struct task_struct *t = current;
> @@ -398,9 +388,11 @@ static int rseq_ip_fixup(struct pt_regs
> */
> if (!in_rseq_cs(ip, &rseq_cs))
> return clear_rseq_cs(t->rseq);
> - ret = rseq_need_restart(t, rseq_cs.flags);
> - if (ret <= 0)
> + ret = rseq_check_flags(t, rseq_cs.flags);
> + if (ret < 0)
> return ret;
> + if (!abort)
Sorry I'm missing context. Which prior patch introduces this "abort"
variable ?
The rest looks good,
Thanks,
Mathieu
> + return 0;
> ret = clear_rseq_cs(t->rseq);
> if (ret)
> return ret;
> @@ -430,14 +422,44 @@ void __rseq_handle_notify_resume(struct
> return;
>
> /*
> - * regs is NULL if and only if the caller is in a syscall path. Skip
> - * fixup and leave rseq_cs as is so that rseq_sycall() will detect and
> - * kill a misbehaving userspace on debug kernels.
> + * If invoked from hypervisors or IO-URING, then @regs is a NULL
> + * pointer, so fixup cannot be done. If the syscall which led to
> + * this invocation was invoked inside a critical section, then it
> + * will either end up in this code again or a possible violation of
> + * a syscall inside a critical region can only be detected by the
> + * debug code in rseq_syscall() in a debug enabled kernel.
> */
> if (regs) {
> - ret = rseq_ip_fixup(regs);
> - if (unlikely(ret < 0))
> - goto error;
> + /*
> + * Read and clear the event mask first. If the task was not
> + * preempted or migrated or a signal is on the way, there
> + * is no point in doing any of the heavy lifting here on
> + * production kernels. In that case TIF_NOTIFY_RESUME was
> + * raised by some other functionality.
> + *
> + * This is correct because the read/clear operation is
> + * guarded against scheduler preemption, which makes it CPU
> + * local atomic. If the task is preempted right after
> + * re-enabling preemption then TIF_NOTIFY_RESUME is set
> + * again and this function is invoked another time _before_
> + * the task is able to return to user mode.
> + *
> + * On a debug kernel, invoke the fixup code unconditionally
> + * with the result handed in to allow the detection of
> + * inconsistencies.
> + */
> + u32 event_mask;
> +
> + scoped_guard(RSEQ_EVENT_GUARD) {
> + event_mask = t->rseq_event_mask;
> + t->rseq_event_mask = 0;
> + }
> +
> + if (IS_ENABLED(CONFIG_DEBUG_RSEQ) || event_mask) {
> + ret = rseq_ip_fixup(regs, !!event_mask);
> + if (unlikely(ret < 0))
> + goto error;
> + }
> }
> if (unlikely(rseq_update_cpu_node_id(t)))
> goto error;
>
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2025-08-20 14:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 16:29 [patch 00/11] rseq: Optimize exit to user space Thomas Gleixner
2025-08-13 16:29 ` [patch 01/11] rseq: Avoid pointless evaluation in __rseq_notify_resume() Thomas Gleixner
2025-08-20 14:23 ` Mathieu Desnoyers [this message]
2025-08-13 16:29 ` [patch 02/11] rseq: Condense the inline stubs Thomas Gleixner
2025-08-20 14:24 ` Mathieu Desnoyers
2025-08-13 16:29 ` [patch 03/11] rseq: Rename rseq_syscall() to rseq_debug_syscall_exit() Thomas Gleixner
2025-08-20 14:25 ` Mathieu Desnoyers
2025-08-13 16:29 ` [patch 04/11] rseq: Replace the pointless event mask bit fiddling Thomas Gleixner
2025-08-13 16:29 ` [patch 05/11] rseq: Optimize the signal delivery path Thomas Gleixner
2025-08-13 16:29 ` [patch 06/11] rseq: Optimize exit to user space further Thomas Gleixner
2025-08-13 16:29 ` [patch 07/11] entry: Cleanup header Thomas Gleixner
2025-08-13 17:09 ` Giorgi Tchankvetadze
2025-08-13 21:30 ` Thomas Gleixner
2025-08-13 16:29 ` [patch 08/11] entry: Distinguish between syscall and interrupt exit Thomas Gleixner
2025-08-13 16:29 ` [patch 09/11] entry: Provide exit_to_user_notify_resume() Thomas Gleixner
2025-08-13 16:29 ` [patch 10/11] rseq: Skip fixup when returning from a syscall Thomas Gleixner
2025-08-14 8:54 ` Peter Zijlstra
2025-08-14 13:24 ` Thomas Gleixner
2025-08-13 16:29 ` [patch 11/11] rseq: Convert to masked user access where applicable Thomas Gleixner
2025-08-13 17:45 ` [patch 00/11] rseq: Optimize exit to user space Jens Axboe
2025-08-13 21:32 ` Thomas Gleixner
2025-08-13 21:36 ` Jens Axboe
2025-08-13 22:08 ` Thomas Gleixner
2025-08-17 21:23 ` Thomas Gleixner
2025-08-18 14:00 ` BUG: rseq selftests and librseq vs. glibc fail Thomas Gleixner
2025-08-18 14:15 ` Florian Weimer
2025-08-18 17:13 ` Thomas Gleixner
2025-08-18 19:33 ` Florian Weimer
2025-08-18 19:46 ` Sean Christopherson
2025-08-18 19:55 ` Florian Weimer
2025-08-18 20:27 ` Sean Christopherson
2025-08-18 23:54 ` Thomas Gleixner
2025-08-19 0:28 ` Sean Christopherson
2025-08-19 6:18 ` Florian Weimer
2025-08-29 18:44 ` Prakash Sangappa
2025-08-29 18:50 ` Mathieu Desnoyers
2025-09-01 19:30 ` Prakash Sangappa
2025-08-18 17:38 ` [patch 00/11] rseq: Optimize exit to user space Michael Jeanson
2025-08-18 20:21 ` Thomas Gleixner
2025-08-18 21:29 ` Michael Jeanson
2025-08-18 23:43 ` Thomas Gleixner
2025-08-20 14:27 ` Mathieu Desnoyers
2025-08-20 14:10 ` 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=8fdb9b21-a918-44bb-b9a0-cd8cbe6379c7@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=axboe@kernel.dk \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjeanson@efficios.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=wei.liu@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®