Re: [mm -next] mapping->tree_lock inconsistent lock state

From	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Newsgroups	linux.kernel
Subject	Re: [mm -next] mapping->tree_lock inconsistent lock state
Date	2016-02-04 01:20 +0100
Message-ID	<qYfOp-Yj-1@gated-at.bofh.it> (permalink)
References	<qY7Hb-3L6-1@gated-at.bofh.it> <qYaF6-5Ec-59@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On (02/03/16 13:45), Johannes Weiner wrote:
> On Thu, Feb 04, 2016 at 12:36:33AM +0900, Sergey Senozhatsky wrote:
> > Hello,
> > 
> > next-20160203
> > 
> > [ 3587.997451] =================================
> > [ 3587.997453] [ INFO: inconsistent lock state ]
> > [ 3587.997456] 4.5.0-rc2-next-20160203-dbg-00007-g37a0a9d-dirty #377 Not tainted
> > [ 3587.997457] ---------------------------------
> > [ 3587.997459] inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage.
> 
> Thanks Sergey. Vladimir sent a patch to move mem_cgroup_migrate() out
> of the IRQ-disabled section:
> 
> http://marc.info/?l=linux-mm&m=145452460721208&w=2
> 
> It looks like Vladimir's original message didn't make it to linux-mm,
> only my reply to it; CC Ben LaHaise.

Thanks Johannes. Will test it (well, just in case) later today.

	-ss

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[mm -next] mapping->tree_lock inconsistent lock state Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-02-03 16:40 +0100
  Re: [mm -next] mapping->tree_lock inconsistent lock state Johannes Weiner <hannes@cmpxchg.org> - 2016-02-03 19:50 +0100
    Re: [mm -next] mapping->tree_lock inconsistent lock state Benjamin LaHaise <bcrl@kvack.org> - 2016-02-03 20:10 +0100
    Re: [mm -next] mapping->tree_lock inconsistent lock state Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2016-02-04 01:20 +0100

csiph-web