netdev - Re: more fallout from sch locking changes?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1466490181.6850.30.camel@edumazet-glaptop3.roam.corp.google.com>
Date:	Mon, 20 Jun 2016 23:23:01 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	David Ahern <dsa@...ulusnetworks.com>
Cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: more fallout from sch locking changes?

On Mon, 2016-06-20 at 22:02 -0600, David Ahern wrote:
> I just updated to top of next-net tree (697666eac66) and still seeing an 
> occasional lockdep splat. It is not reliable to the point I would 
> attempt a git bisect. 2 splats -- 1 for ipv4 (first login to VM after 
> boot) and ipv6 (second login to VM after boot). Perhaps it is more 
> fallout of the packet scheduling changes you have been making this 
> iteration. Just a guess based on sch_direct_xmit in both traces.

Seems to be a lockdep hash chain collision, please report to lkml.