From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] rcu: Allow for page faults in NMI handlers" failed to apply to 4.9-stable tree
Date: Thu, 12 Oct 2017 16:14:52 -0700 [thread overview]
Message-ID: <20171012231452.GU3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171002154748.1f1227c2@gandalf.local.home>
On Mon, Oct 02, 2017 at 03:47:48PM -0400, Steven Rostedt wrote:
> On Mon, 2 Oct 2017 12:38:57 -0700
> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
>
> > On Mon, Oct 02, 2017 at 03:33:17PM -0400, Steven Rostedt wrote:
> > >
> > > Paul,
> > >
> > > Can you backport this patch to 4.9 and 4.4 if it is required. The other
> > > patches I posted (and also failed to apply, but should be backported)
> > > depend on this patch, if it is an issue with those kernels.
> >
> > No problem!
> >
> > How do we determine whether or not it is required?
>
> Can rcu_irq_enter() be called within a rcu_nmi_enter() in these
> kernels? If not, that needs to be fixed. Because nmi's can still page
> fault.
>
> >
> > Do we need to ask one of Bruce or Nick? ;-)
> >
>
> The bug I fixed is actually there, but lockdep doesn't complain. The
> module code that uses synchronize_sched() which requires RCU to be
> watching when preemption is disabled. RCU isn't watching is some of
> these cases that are called. Recent kernels added rcu annotations into
> these preempt disabled paths which caused lockdep to report the issue.
> The older kernels that had the bug just didn't have lockdep complain
> about it.
It turned out that one backport is needed for 4.2-4.4, and another
for 4.5-4.12. I sent both.
Thanx, Paul
prev parent reply other threads:[~2017-10-12 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 11:44 FAILED: patch "[PATCH] rcu: Allow for page faults in NMI handlers" failed to apply to 4.9-stable tree gregkh
2017-10-02 19:33 ` Steven Rostedt
2017-10-02 19:38 ` Paul E. McKenney
2017-10-02 19:47 ` Steven Rostedt
2017-10-12 23:14 ` Paul E. McKenney [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=20171012231452.GU3521@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.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 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.