[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141204003024.GA17665@redhat.com>
Date: Wed, 3 Dec 2014 19:30:24 -0500
From: Dave Jones <davej@...hat.com>
To: Andy Lutomirski <luto@...capital.net>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Richard Guy Briggs <rgb@...hat.com>,
Eric Paris <eparis@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Oleg Nesterov <oleg@...hat.com>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCH] context_tracking: Restore previous state in schedule_user
On Wed, Dec 03, 2014 at 04:04:31PM -0800, Andy Lutomirski wrote:
> On Wed, Dec 3, 2014 at 3:58 PM, Frederic Weisbecker <fweisbec@...il.com> wrote:
> > On Wed, Dec 03, 2014 at 03:18:41PM -0800, Andy Lutomirski wrote:
> >> It appears that some SCHEDULE_USER (asm for schedule_user) callers
> >> in arch/x86/kernel/entry_64.S are called from RCU kernel context,
> >> and schedule_user will return in RCU user context. This causes RCU
> >> warnings and possible failures.
> >>
> >> This is intended to be a minimal fix suitable for 3.18.
> >>
> >> Reported-by: Dave Jones <davej@...hat.com>
> >> Cc: Oleg Nesterov <oleg@...hat.com>
> >> Cc: Frédéric Weisbecker <fweisbec@...il.com>
> >> Cc: Paul McKenney <paulmck@...ux.vnet.ibm.com>
> >> Signed-off-by: Andy Lutomirski <luto@...capital.net>
> >
> > Ah, we sent it about at the same time :-)
> >
> > Might be too late for 3.18 though because it's not a regression.
Wait, so how come that trace didn't start showing up until recently ?
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists