[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160203184509.GB4007@cmpxchg.org>
Date: Wed, 3 Feb 2016 13:45:09 -0500
From: Johannes Weiner <hannes@...xchg.org>
To: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Michal Hocko <mhocko@...nel.org>,
Vladimir Davydov <vdavydov@...tuozzo.com>,
Vlastimil Babka <vbabka@...e.cz>, cgroups@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Benjamin LaHaise <bcrl@...ck.org>
Subject: Re: [mm -next] mapping->tree_lock inconsistent lock state
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.
Powered by blists - more mailing lists