From: "David S. Miller" <davem@davemloft.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: kaber@trash.net, netdev@oss.sgi.com
Subject: Re: [IPSEC]: Protect against BHs in xfrm_user_policy()
Date: Mon, 4 Apr 2005 10:35:09 -0700 [thread overview]
Message-ID: <20050404103509.06ca48a4.davem@davemloft.net> (raw)
In-Reply-To: <20050404115508.GA12171@gondor.apana.org.au>
On Mon, 4 Apr 2005 21:55:08 +1000
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> The read_lock()'s only need to be protected from the write_lock()'s.
>
> Since all the write_lock()'s are made in process context, we don't
> need to disable BH on the read_lock()'s.
This is correct.
It's actually a common technique, only disable IRQ or BH in
the write_locks.
prev parent reply other threads:[~2005-04-04 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 16:13 [IPSEC]: Protect against BHs in xfrm_user_policy() Patrick McHardy
2005-04-04 1:20 ` Herbert Xu
2005-04-04 3:47 ` Patrick McHardy
2005-04-04 4:06 ` Herbert Xu
2005-04-04 11:55 ` Herbert Xu
2005-04-04 17:35 ` 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=20050404103509.06ca48a4.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kaber@trash.net \
--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;
as well as URLs for NNTP newsgroup(s).