[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180417100705.qd57z42h7ajxu24i@ninjato>
Date: Tue, 17 Apr 2018 12:07:05 +0200
From: Wolfram Sang <wsa@...-dreams.de>
To: Simon Horman <horms+renesas@...ge.net.au>
Cc: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
Magnus Damm <magnus.damm@...il.com>, netdev@...r.kernel.org,
linux-renesas-soc@...r.kernel.org,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Masaru Nagai <masaru.nagai.vx@...esas.com>,
Kazuya Mizuguchi <kazuya.mizuguchi.ks@...esas.com>
Subject: Re: [PATCH/RFC net-next 1/5] ravb: fix inconsistent lock state at
enabling tx timestamp
On Tue, Apr 17, 2018 at 10:50:26AM +0200, Simon Horman wrote:
> From: Masaru Nagai <masaru.nagai.vx@...esas.com>
>
> [ 58.490829] =================================
> [ 58.495205] [ INFO: inconsistent lock state ]
> [ 58.499583] 4.9.0-yocto-standard-00007-g2ef7caf #57 Not tainted
> [ 58.505529] ---------------------------------
> [ 58.509904] inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
> [ 58.515939] swapper/0/0 [HC1[1]:SC1[1]:HE0:SE0] takes:
> [ 58.521099] (&(&list->lock)->rlock#2){?.-...}, at: [<ffff00000899f474>] skb_queue_tail+0x2c/0x68
> {HARDIRQ-ON-W} state was registered at:
Maybe add a short text to the log to describe the approach of this fix?
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists