linux-kernel - Re: possible recursive locking in udp4_lib

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: <20080808150825.GA18199@google.com>
Date:	Fri, 8 Aug 2008 18:08:26 +0300
From:	"Michael S. Tsirkin" <m.s.tsirkin@...il.com>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	linux-kernel@...r.kernel.org, davem@...emloft.net,
	yoshfuji@...ux-ipv6.org, netdev@...r.kernel.org, haoki@...hat.com
Subject: Re: possible recursive locking in udp4_lib_rcv

On Fri, Aug 08, 2008 at 11:01:08PM +0800, Herbert Xu wrote:
> On Fri, Aug 08, 2008 at 10:37:41PM +0800, Herbert Xu wrote:
> >
> > Never mind, I see the reason why it's there.  What we should do
> > is drop the lock when we hit an encapsulated socket since they
> > don't need it at all.
> 
> Here is the patch:

Nice. Open a bugzilla entry for this?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/