From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Shawn Guo <shawn.guo@freescale.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Stephen Hemminger <stephen@networkplumber.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Inconsistent lock state introduced by ipv6/addrconf change
Date: Fri, 4 Apr 2014 13:48:48 +0200 [thread overview]
Message-ID: <20140404114848.GD13354@order.stressinduktion.org> (raw)
In-Reply-To: <20140404073455.GB29778@dragon>
Hello!
On Fri, Apr 04, 2014 at 03:34:56PM +0800, Shawn Guo wrote:
> I'm running into an inconsistent lock state warning on the final v3.14
> kernel (-rc8 is good) on Freescale i.MX6 platform with fec driver
> (drivers/net/ethernet/freescale/fec_main.c). The git bisect points
> the finger to commit c15b1cc (ipv6: move DAD and addrconf_verify
> processing to workqueue). Reverting the commit does fix the problem
> for me. The image is built from arch/arm/configs/imx_v6_v7_defconfig.
>
> The interesting part is the same warning shows up on mainline tree until
> net-next gets merged with commit cd6362b. That's why Olof's autobooter
> keeps reporting failure on hummingboard and wandboard (both i.MX6 based)
> since v3.14 release [1], but reports success after commit cd6362b.
>
> We're less concerned by the mainline tree, since the problem disappeared
> now (nice to know why though). But we do still want to fix it for 3.14
> stable kernel.
The patch which fixes this is already queued up for -stable:
http://patchwork.ozlabs.org/patch/335536/
Sorry for the inconvenience,
Hannes
next prev parent reply other threads:[~2014-04-04 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 7:34 Inconsistent lock state introduced by ipv6/addrconf change Shawn Guo
2014-04-04 11:48 ` Hannes Frederic Sowa [this message]
2014-04-04 15:09 ` Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140404114848.GD13354@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shawn.guo@freescale.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).