[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kvm
Subject:    Re: async pf: INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected
From:       "Paul E. McKenney" <paulmck () linux ! vnet ! ibm ! com>
Date:       2012-04-27 18:14:50
Message-ID: 20120427181450.GF2534 () linux ! vnet ! ibm ! com
[Download RAW message or body]

On Fri, Apr 27, 2012 at 08:05:15PM +0200, Sasha Levin wrote:
> On Fri, Apr 27, 2012 at 5:23 PM, Paul E. McKenney
> <paulmck@linux.vnet.ibm.com> wrote:
> >
> > On Thu, Apr 26, 2012 at 04:50:35PM +0200, Sasha Levin wrote:
> > > Hi all.
> > >
> > > I got a "INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected"
> > > warning
> > > while running LTP inside a KVM guest using the recent -next kernel.
> > >
> > > It seems that it was initially originated from rcu_torture_rea(), but I
> > > don't think that it's a problem with RCU itself (I'll cc. Paul just in
> > > case). RCU torture was indeed configured to run during the testing.
> >
> > I might be missing something, but I don't see how RCU is involved in
> > this one.
> 
> It happened due to a rcutorture thread:
> 
> [ 4248.579019] rcu_torture_rea/1615 [HC0[0]:SC0[0]:HE0:SE1] is trying
> to acquire:
> [ 4248.579019]  (pgd_lock){+.+...}, at: [<ffffffff81089476>] pgd_free+0x26/0xa0
> 
> rcutorture has never triggered anything on my tests up until now, and
> is probably not responsible for the actual warning in this case, just
> figured I should cc you in case I'm wrong :)

No worries!

I only responded on the off-chance that everyone else was waiting on
me to identify the bug and provide the fix.  ;-)

							Thanx, Paul

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]