[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <176911.1461527778@turing-police.cc.vt.edu>
Date: Sun, 24 Apr 2016 15:56:18 -0400
From: Valdis.Kletnieks@...edu
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Hannes Frederic Sowa <hannes@...essinduktion.org>,
David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: linux-next: zillions of lockdep whinges in include/net/sock.h:1408
On Sun, 24 Apr 2016 12:46:42 -0700, Eric Dumazet said:
> >>> + return !debug_locks ||
> >>> + lockdep_is_held(&sk->sk_lock) ||
> Issue here is that once lockdep detected a problem (not necessarily in
> net/ tree btw), your helper always 'detect' a problem, since lockdep
> automatically disables itself.
"D'Oh!" -- H. Simpson
I thought this patch looked suspect, but couldn't put my finger on it. The
reason why I got like 41,000 of them is because I built a kernel that has
lockdep enabled, but I have an out-of-tree module that doesn't init something,
so I get this:
[ 48.898156] INFO: trying to register non-static key.
[ 48.898157] the code is fine but needs lockdep annotation.
[ 48.898157] turning off the locking correctness validator.
After which point, even with this patch, every time through it's still going to
explode.
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists