From: Keith Owens <kaos@ocs.com.au>
To: Patrick Mochel <mochel@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Driverfs updates
Date: Tue, 09 Jul 2002 09:33:24 +1000 [thread overview]
Message-ID: <21467.1026171204@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 08 Jul 2002 11:41:52 MST." <Pine.LNX.4.33.0207051554580.961-100000@geena.pdx.osdl.net>
On Mon, 8 Jul 2002 11:41:52 -0700 (PDT),
Patrick Mochel <mochel@osdl.org> wrote:
>- Add struct module * owner field to struct device_driver
>- Change {get,put}_driver to use it
struct device_driver * get_driver(struct device_driver * drv)
{
if (drv && drv->owner)
if (!try_inc_mod_count(drv->owner))
return NULL;
return drv;
}
is racy. The module can be unloaded after if (drv->owner) and before
try_inc_mod_count. To prevent that race, drv itself must be locked
around calls to get_driver().
The "normal" method is to have a high level lock that controls the drv
list and to take that lock in the register and unregister routines and
around the call to try_inc_mod_count. drv->bus->lock is no good,
anything that relies on reading drv without a lock or module reference
count is racy. I suggest you add a global driverfs_lock.
next prev parent reply other threads:[~2002-07-08 23:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 18:41 Patrick Mochel
2002-07-08 23:33 ` Keith Owens [this message]
2002-07-08 23:52 ` Thunder from the hill
2002-07-09 0:09 ` Keith Owens
2002-07-09 8:30 ` Oliver Neukum
2002-07-09 11:08 ` Thunder from the hill
2002-07-09 11:45 ` Richard B. Johnson
2002-07-09 12:20 ` David D. Hagood
2002-07-09 12:33 ` Thunder from the hill
2002-07-09 14:43 ` jbradford
2002-07-10 7:15 ` jw schultz
2002-07-09 17:05 ` Oliver Neukum
2002-07-10 0:43 ` Pavel Machek
2002-07-09 16:56 ` Patrick Mochel
2002-07-09 23:29 ` Keith Owens
2002-07-10 20:02 ` Patrick Mochel
2002-07-11 0:40 ` John Alvord
2002-07-18 18:11 driverfs updates Patrick Mochel
2002-07-18 18:33 ` Greg KH
2002-07-18 19:57 ` Patrick Mochel
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=21467.1026171204@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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 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®