From: "Michael S. Tsirkin" <m.s.tsirkin@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
yoshfuji@linux-ipv6.org, netdev@vger.kernel.org,
haoki@redhat.com
Subject: Re: possible recursive locking in udp4_lib_rcv
Date: Fri, 8 Aug 2008 18:08:26 +0300 [thread overview]
Message-ID: <20080808150825.GA18199@google.com> (raw)
In-Reply-To: <20080808150108.GA21048@gondor.apana.org.au>
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?
next prev parent reply other threads:[~2008-08-08 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 23:46 possible recursive locking in udp4_lib_rcv Michael S. Tsirkin
2008-08-08 14:28 ` Herbert Xu
2008-08-08 14:37 ` Herbert Xu
2008-08-08 15:01 ` Herbert Xu
2008-08-08 15:08 ` Michael S. Tsirkin [this message]
2008-08-09 3:50 ` Hideo AOKI
2008-08-09 7:36 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080808150825.GA18199@google.com \
--to=m.s.tsirkin@gmail.com \
--cc=davem@davemloft.net \
--cc=haoki@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).