lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 4 Apr 2014 13:48:48 +0200
From:	Hannes Frederic Sowa <>
To:	Shawn Guo <>
	Stephen Hemminger <>,
	"David S. Miller" <>
Subject: Re: Inconsistent lock state introduced by ipv6/addrconf change


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:

Sorry for the inconvenience,


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists