All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Frederic Weisbecker <frederic@kernel.org>,
	Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	Uladzislau Rezki <urezki@gmail.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the rcu tree with the ftrace tree
Date: Fri, 14 Nov 2025 14:35:32 +0100	[thread overview]
Message-ID: <20251114133532.mmdi2dca@linutronix.de> (raw)
In-Reply-To: <20251114074255.3e535084@gandalf.local.home>

On 2025-11-14 07:42:55 [-0500], Steven Rostedt wrote:
> > diff --cc kernel/trace/trace_syscalls.c
> > index e96d0063cbcf,3f699b198c56..000000000000
> > --- a/kernel/trace/trace_syscalls.c
> > +++ b/kernel/trace/trace_syscalls.c
> > @@@ -878,6 -322,8 +890,7 @@@ static void ftrace_syscall_enter(void *
> >   	 * buffer and per-cpu data require preemption to be disabled.
> >   	 */
> >   	might_fault();
> > + 	preempt_rt_guard();
> >  -	guard(preempt_notrace)();
> 
> My code made it so that preemption is not needed here but is moved later
> down for the logic that does the reading of user space data.
> 
> Note, it must have preemption disabled for all configs (including RT).
> Otherwise, the data it has can get corrupted.
> 
> Paul, can you change it so that you *do not* touch this file?

Where is preempt_rt_guard() from?

> Thanks,
> 
> -- Steve

Sebastian

  reply	other threads:[~2025-11-14 13:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14  2:52 linux-next: manual merge of the rcu tree with the ftrace tree Stephen Rothwell
2025-11-14 12:42 ` Steven Rostedt
2025-11-14 13:35   ` Sebastian Andrzej Siewior [this message]
2025-11-14 15:46     ` Steven Rostedt
2025-11-14 16:00       ` Sebastian Andrzej Siewior
2025-11-14 16:22         ` Steven Rostedt
2025-11-14 16:33           ` Sebastian Andrzej Siewior
2025-11-14 16:48             ` Steven Rostedt
2025-11-14 17:02               ` Sebastian Andrzej Siewior
2025-11-14 17:11                 ` Steven Rostedt
2025-11-14 17:00             ` Paul E. McKenney
2025-11-14 17:10               ` Sebastian Andrzej Siewior
2025-11-14 17:25                 ` Paul E. McKenney
2025-11-14 17:40                   ` Steven Rostedt
2025-11-14 17:41                   ` Sebastian Andrzej Siewior
2025-11-14 18:26                     ` Paul E. McKenney
2025-11-14 14:48   ` Frederic Weisbecker
2025-11-14 16:01     ` Steven Rostedt
2025-11-14 17:06     ` Paul E. McKenney
2025-11-14 18:58       ` Paul E. McKenney
2025-11-18 13:05       ` Frederic Weisbecker
2025-11-18 15:04         ` Paul E. McKenney
2025-12-02  0:57           ` Paul E. McKenney
2025-12-07 20:43             ` Paul E. McKenney
2025-12-08  0:17               ` Steven Rostedt
2025-12-08  4:21                 ` Paul E. McKenney
2025-11-14 17:05   ` Paul E. McKenney
2025-11-14 18:31     ` Yonghong Song
2025-11-18  7:35       ` Sebastian Andrzej Siewior
2025-11-18 15:05         ` Paul E. McKenney
2025-11-30 18:49         ` Yonghong Song
2025-11-19  0:38     ` Paul E. McKenney
  -- strict thread matches above, loose matches on Subject: below --
2025-11-06  1:24 Stephen Rothwell
2017-05-01  3:18 Stephen Rothwell

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=20251114133532.mmdi2dca@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=boqun.feng@gmail.com \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=neeraj.upadhyay@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sfr@canb.auug.org.au \
    --cc=urezki@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.