From: David Miller <davem@davemloft.net>
To: dada1@cosmosbay.com
Cc: a.beregalov@gmail.com, mchan@broadcom.com,
linux-next@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: UDP/bnx2: inconsistent lock state
Date: Thu, 30 Oct 2008 14:01:34 -0700 (PDT) [thread overview]
Message-ID: <20081030.140134.68573546.davem@davemloft.net> (raw)
In-Reply-To: <4909B4D9.20807@cosmosbay.com>
From: Eric Dumazet <dada1@cosmosbay.com>
Date: Thu, 30 Oct 2008 14:21:29 +0100
> [PATCH] udp: Should use spin_lock_bh()/spin_unlock_bh() in udp_lib_unhash()
>
> Spotted by Alexander Beregalov
>
> Signed-off-by: Eric Dumazet <dada1@cosmosbay.com>
Applied, thanks for fixing this so quickly Eric.
prev parent reply other threads:[~2008-10-30 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 10:40 UDP/bnx2: inconsistent lock state (Re: linux-next: Tree for October 30) Alexander Beregalov
2008-10-30 12:59 ` Alexander Beregalov
2008-10-30 13:22 ` Eric Dumazet
2008-10-30 13:21 ` Eric Dumazet
2008-10-30 21:01 ` David Miller [this message]
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=20081030.140134.68573546.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.beregalov@gmail.com \
--cc=dada1@cosmosbay.com \
--cc=linux-next@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.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).