netdev - Re: [RFT] proxy arp deadlock possible

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 PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

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

Date:	Wed, 04 Apr 2007 18:10:42 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	davem@...emloft.net, mingo@...e.hu, davej@...hat.com,
	netdev@...r.kernel.org
Subject: Re: [RFT] proxy arp deadlock possible

On Thu, 2007-04-05 at 10:44 +1000, Herbert Xu wrote:
> Stephen Hemminger <shemminger@...ux-foundation.org> wrote:
> > Thanks Dave, there is a classic AB BA deadlock here.
> > We should break the dependency like this.
> > 
> > Could someone who uses proxy ARP test this?
> 
> Sorry Stephen, this isn't necessary.  The lockdep thing is
> simply confused here.  It's treating tbl->proxy_queue as the
> same thing as neigh->arp_queue when they're clearly different.
> 
> I'm disappointed that after all this time lockdep is still
> producing bogus reports like this.  I'm sure we've been
> through this particular issue many times already.


what's the exact lockdep output here?

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

-
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