From: Paul McKenney <Paul.McKenney@us.ibm.com>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: David Miller <davem@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"" <linux-kernel-owner@vger.kernel.org>,
"" <linux-net@vger.kernel.org>,
Stephen Hemminger <shemminger@osdl.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] (1/8) Eliminate brlock in psnap
Date: Thu, 13 Mar 2003 13:54:49 -0800 [thread overview]
Message-ID: <OFC402C478.7A88360D-ON88256CE8.00785BB5@us.ibm.com> (raw)
> > Module unloading should be rare enough to tolerate
> > the grace period under the module_mutex, right?
> >
> > Thoughts?
>
> I would agree. However can't unregister_snap_client be used in other
paths
> apart from module_unload? I wouldn't worry too much since if
> register_snap_client and unregister_snap_client for the same protocol
> races it's a bug in the caller's code. The safe RCU list removal and
> synchronize_kernel should protect us from sane usage.
>
> Zwane
It is not called from elsewhere right now, but if there
is a possibility that it might be, Steve of course should
keep the locking in these functions.
Thanx, Paul
next reply other threads:[~2003-03-13 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 21:54 Paul McKenney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 20:28 Paul McKenney
2003-03-13 0:54 ` Zwane Mwaikambo
2003-03-10 2:33 [PATCH] small fixes in brlock.h Linus Torvalds
2003-03-12 0:14 ` [PATCH] (1/8) Eliminate brlock in psnap Stephen Hemminger
2003-03-12 1:03 ` Roman Zippel
2003-03-12 1:13 ` Zwane Mwaikambo
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=OFC402C478.7A88360D-ON88256CE8.00785BB5@us.ibm.com \
--to=paul.mckenney@us.ibm.com \
--cc=davem@redhat.com \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=torvalds@transmeta.com \
--cc=zwane@holomorphy.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
all inboxes | Powered by JetHome®