From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
rcu@vger.kernel.org, joel@joelfernandes.org
Subject: Re: [GIT PULL rcu/urgent] Don't acquire lock in NMI handler (v5.7)
Date: Tue, 14 Apr 2020 08:37:39 +0200 [thread overview]
Message-ID: <20200414063739.GE84326@gmail.com> (raw)
In-Reply-To: <20200406011036.GA1435@paulmck-ThinkPad-P72>
* Paul E. McKenney <paulmck@kernel.org> wrote:
> Hello!
>
> This pull request contains a single commit that avoid acquiring
> a lock when rcu_nmi_enter_common() is invoked from an NMI handler.
> This issue can of course result in self-deadlock, and the fix is quite
> straightforward. I am therefore putting it forward for the current
> release (v5.7) instead of following my normal process, which would
> delay it until v5.8.
>
> This fix has been subjected to rcutorture, kbuild test robot, and -next
> testing and is available at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git urgent-for-mingo
>
> for you to fetch changes up to bf37da98c51825c90432d340e135cced37a7460d:
>
> rcu: Don't acquire lock in NMI handler in rcu_nmi_enter_common() (2020-04-05 14:22:15 -0700)
>
> ----------------------------------------------------------------
> Paul E. McKenney (1):
> rcu: Don't acquire lock in NMI handler in rcu_nmi_enter_common()
>
> kernel/rcu/tree.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Pulled into tip:core/urgent, thanks Paul!
Ingo
prev parent reply other threads:[~2020-04-14 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 1:10 [GIT PULL rcu/urgent] Don't acquire lock in NMI handler (v5.7) Paul E. McKenney
2020-04-14 6:37 ` Ingo Molnar [this message]
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=20200414063739.GE84326@gmail.com \
--to=mingo@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--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