From: jamal <hadi@cyberus.ca>
To: Patrick McHardy <kaber@trash.net>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Masahide NAKAMURA <nakam@linux-ipv6.org>,
"David S. Miller" <davem@davemloft.net>,
netdev <netdev@oss.sgi.com>
Subject: Re: take 2 WAS(Re: PATCH: IPSEC xfrm events
Date: 03 Apr 2005 12:36:35 -0400 [thread overview]
Message-ID: <1112546194.1096.401.camel@jzny.localdomain> (raw)
In-Reply-To: <42501027.6010609@trash.net>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
Masahide,
Attached is incremental patch on top of the one posted earlier.
Looks ok from my basic testing. Please run it against your tests
and see if it stands.
cheers,
jamal
On Sun, 2005-04-03 at 11:47, Patrick McHardy wrote:
> You call these functions from both softirq- and user-context, so you
> need to protect against BHs.
>
> Regards
> Patrick
>
[-- Attachment #2: ipsec-event-take2-1-1 --]
[-- Type: text/plain, Size: 704 bytes --]
--- a/net/xfrm/xfrm_state.c 2005/04/03 16:30:31 1.2
+++ b/net/xfrm/xfrm_state.c 2005/04/03 16:31:27
@@ -251,20 +251,20 @@
{
struct xfrm_mgr *km;
- read_lock(&xfrm_km_lock);
+ read_lock_bh(&xfrm_km_lock);
list_for_each_entry(km, &xfrm_km_list, list)
if (km->notify_policy)
km->notify_policy(xp, dir, c);
- read_unlock(&xfrm_km_lock);
+ read_unlock_bh(&xfrm_km_lock);
}
void km_state_notify(struct xfrm_state *x, struct km_event *c)
{
struct xfrm_mgr *km;
- read_lock(&xfrm_km_lock);
+ read_lock_bh(&xfrm_km_lock);
list_for_each_entry(km, &xfrm_km_list, list)
km->notify(x, c);
- read_unlock(&xfrm_km_lock);
+ read_unlock_bh(&xfrm_km_lock);
}
EXPORT_SYMBOL(km_policy_notify);
next prev parent reply other threads:[~2005-04-03 16:36 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 1:37 PATCH: IPSEC xfrm events jamal
2005-04-01 4:21 ` Herbert Xu
2005-04-01 11:03 ` jamal
2005-04-01 11:42 ` Herbert Xu
2005-04-01 12:24 ` jamal
2005-04-01 12:35 ` Herbert Xu
2005-04-01 12:59 ` jamal
2005-04-01 13:18 ` jamal
2005-04-01 14:19 ` Masahide NAKAMURA
2005-04-02 1:04 ` jamal
2005-04-02 1:28 ` Herbert Xu
2005-04-02 1:42 ` jamal
2005-04-02 1:45 ` Herbert Xu
2005-04-02 1:46 ` Herbert Xu
2005-04-02 19:20 ` take 2 WAS(Re: " jamal
2005-04-03 14:31 ` jamal
2005-04-03 15:47 ` Patrick McHardy
2005-04-03 16:29 ` jamal
2005-04-03 16:36 ` jamal [this message]
2005-04-04 0:58 ` Herbert Xu
2005-04-04 1:56 ` jamal
2005-04-04 2:26 ` Herbert Xu
2005-04-04 2:39 ` jamal
2005-04-04 2:46 ` Herbert Xu
2005-04-04 3:05 ` jamal
2005-04-04 2:34 ` jamal
2005-04-04 2:52 ` Herbert Xu
2005-04-04 3:07 ` jamal
2005-04-04 11:38 ` take 2-2 " jamal
2005-04-04 12:16 ` Herbert Xu
2005-04-04 12:51 ` jamal
2005-04-04 13:02 ` Herbert Xu
2005-04-04 13:16 ` jamal
2005-04-04 21:31 ` Herbert Xu
2005-04-04 22:20 ` jamal
2005-04-04 22:25 ` David S. Miller
2005-04-04 22:42 ` jamal
2005-04-05 7:35 ` Masahide NAKAMURA
2005-04-05 10:18 ` jamal
2005-04-05 10:22 ` Herbert Xu
2005-04-05 10:35 ` jamal
2005-04-05 11:58 ` jamal
2005-04-05 17:46 ` David S. Miller
2005-04-05 18:05 ` jamal
2005-04-04 1:01 ` take 2 " Herbert Xu
2005-04-04 1:58 ` jamal
2005-04-04 2:27 ` Herbert Xu
2005-04-01 17:28 ` Masahide NAKAMURA
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=1112546194.1096.401.camel@jzny.localdomain \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kaber@trash.net \
--cc=nakam@linux-ipv6.org \
--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