From: Peter Zijlstra <peterz@infradead.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: tglx@linutronix.de, sfr@canb.auug.org.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] rcu,sched: noinstr fixes
Date: Wed, 29 Sep 2021 10:39:02 +0200 [thread overview]
Message-ID: <YVQmJqTiplH+/0qL@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210928181559.GD880162@paulmck-ThinkPad-P17-Gen-1>
On Tue, Sep 28, 2021 at 11:15:59AM -0700, Paul E. McKenney wrote:
> On Tue, Sep 28, 2021 at 10:40:20AM +0200, Peter Zijlstra wrote:
> > A few noinstr fixes.. I'll stick the sched one in sched/urgent, Paul could you pick up the other two?
>
> I queued those two, thank you! I am guessing that you are looking for
> me to send them ASAP. If so, not a problem, but please confirm.
Either way works, but given syzcaller could potentially trigger these
holes (it did find a whole bunch of 'interesting' problems in the early
noinstr days) I'd prefer them earlier rather than later.
OTOH, the objtool patches that keep triggering them all over the place
are still in objtool/core for the next cycle.
next prev parent reply other threads:[~2021-09-29 8:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 8:40 Peter Zijlstra
2021-09-28 8:40 ` [PATCH 1/3] rcu: Always inline rcu_dynticks_task*_{enter,exit}() Peter Zijlstra
2021-09-28 22:35 ` Thomas Gleixner
2021-09-28 23:03 ` Paul E. McKenney
2021-09-28 8:40 ` [PATCH 2/3] rcu: Fix rcu_dynticks_curr_cpu_in_eqs() vs noinstr Peter Zijlstra
2021-09-28 22:35 ` Thomas Gleixner
2021-09-28 8:40 ` [PATCH 3/3] sched: Always inline is_percpu_thread() Peter Zijlstra
2021-09-28 22:36 ` Thomas Gleixner
2021-10-01 12:10 ` [tip: sched/urgent] " tip-bot2 for Peter Zijlstra
2021-09-28 18:15 ` [PATCH 0/3] rcu,sched: noinstr fixes Paul E. McKenney
2021-09-29 8:39 ` Peter Zijlstra [this message]
2021-09-29 15:29 ` Paul E. McKenney
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=YVQmJqTiplH+/0qL@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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
Powered by JetHome