From: Jesper Dangaard Brouer <hawk@comx.dk>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: [PATCH 0/5] rcu_barrier: Resubmitting the the networking bits
Date: Fri, 26 Jun 2009 21:31:49 +0200 [thread overview]
Message-ID: <20090626192258.1724.76461.stgit@localhost> (raw)
This patchset is a resubmit of the network related part of a patchseries
titled "We must use rcu_barrier() on module unload". Just to make it
easier for DaveM to pick it up.
If an unloadable module uses RCU callbacks, it need to use
rcu_barrier() so that the module may be safely unloaded.
For documentation see:
Paul E. McKenney's Blog
http://paulmck.livejournal.com/7314.html
http://lwn.net/Articles/217484/
Documentation/RCU/rcubarrier.txt
Patchset is made on top of Linus'es tree, 4075ea8c54a7506844a69f674990241e7766357b.
But I have testet is applies to net-next-2.6.
---
Jesper Dangaard Brouer (5):
decnet: Use rcu_barrier() on module unload.
ipv6: Use rcu_barrier() on module unload.
sunrpc: Use rcu_barrier() on unload.
mac80211: Use rcu_barrier() on unload.
bridge: Use rcu_barrier() instead of syncronize_net() on unload.
net/bridge/br.c | 2 +-
net/decnet/af_decnet.c | 2 ++
net/ipv6/af_inet6.c | 2 ++
net/mac80211/mesh.c | 2 +-
net/sunrpc/sunrpc_syms.c | 1 +
5 files changed, 7 insertions(+), 2 deletions(-)
--
Best regards,
Jesper Brouer
ComX Networks A/S
Linux Network developer
Cand. Scient Datalog / MSc.
Author of http://adsl-optimizer.dk
LinkedIn: http://www.linkedin.com/in/brouer
next reply other threads:[~2009-06-26 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 19:31 Jesper Dangaard Brouer [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-26 20:30 [PATCH 0/5] rcu_barrier: Resubmitting the the networking bits Jesper Dangaard Brouer
2009-06-26 20:45 Jesper Dangaard Brouer
2009-06-26 20:52 ` 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=20090626192258.1724.76461.stgit@localhost \
--to=hawk@comx.dk \
--cc=davem@davemloft.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.