netdev - Re: rtnl_lock deadlock on 3.10

lists.openwall.net		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 linux-hardening linux-cve-announce 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]

Message-ID: <20130702082818.GA26178@order.stressinduktion.org>
Date:	Tue, 2 Jul 2013 10:28:18 +0200
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Shawn Bohrer <sbohrer@...advisors.com>
Cc:	netdev@...r.kernel.org
Subject: Re: rtnl_lock deadlock on 3.10

On Mon, Jul 01, 2013 at 09:54:56AM -0500, Shawn Bohrer wrote:
> I've managed to hit a deadlock at boot a couple times while testing
> the 3.10 rc kernels.  It seems to always happen when my network
> devices are initializing.  This morning I updated to v3.10 and made a
> few config tweaks and so far I've hit it 4 out of 5 reboots.  It looks
> like most processes are getting stuck on rtnl_lock.  Below is a boot
> log with the soft lockup prints.  Please let know if there is any
> other information I can provide:

Could you try a build with CONFIG_LOCKDEP enabled?

Thanks,

  Hannes

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html