From: "David S. Miller" <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: netdev@oss.sgi.com
Subject: Re: [IPV4/IPV6] Replace spin_lock_irq with spin_lock_bh
Date: Thu, 02 Jun 2005 22:10:26 -0700 (PDT) [thread overview]
Message-ID: <20050602.221026.112287995.davem@davemloft.net> (raw)
In-Reply-To: <20050602094404.GA10316@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Thu, 2 Jun 2005 19:44:04 +1000
> In light of my recent patch to net/ipv4/udp.c that replaced the
> spin_lock_irq calls on the receive queue lock with spin_lock_bh,
> here is a similar patch for all other occurences of spin_lock_irq
> on receive/error queue locks in IPv4 and IPv6.
>
> In these stacks, we know that they can only be entered from user
> or softirq context. Therefore it's safe to disable BH only.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Applied to net-2.6.13, thanks Herbert.
prev parent reply other threads:[~2005-06-03 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 9:44 [IPV4/IPV6] Replace spin_lock_irq with spin_lock_bh Herbert Xu
2005-06-02 9:54 ` [SCTP] Replace spin_lock_irqsave " Herbert Xu
2005-06-03 5:11 ` David S. Miller
2005-06-03 5:10 ` David S. 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=20050602.221026.112287995.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.com \
/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