From: Mike Waychison <Michael.Waychison@Sun.COM>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Greg KH <greg@kroah.com>, Jirka Kosina <jikos@jikos.cz>,
Patrick Mochel <mochel@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix bad locking in drivers/base/driver.c
Date: Tue, 25 Jan 2005 11:10:46 -0500 [thread overview]
Message-ID: <41F66F86.4000609@sun.com> (raw)
In-Reply-To: <41F64E87.8040501@tmr.com>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bill Davidsen wrote:
>
> Let's clean up the spelling as well
>> - * Though, once that is done, we attempt to take @drv->unload_sem.
>> + * Though, once that is done, we wait until @drv->unloaded is
>> copmleted.
>
> ------------------------------------------------------------------>completed
Thanks for pointing that out. Updated patch attached.
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB9m+FdQs4kOxk3/MRAtusAJ9S+DSVR4DaAK2fLHquYzgRxamq7ACfZNSN
LkPoYAx27W1MpHiW24RL2yM=
=HBQX
-----END PGP SIGNATURE-----
[-- Attachment #2: convert_unload_sem_to_completion.patch --]
[-- Type: text/x-patch, Size: 3045 bytes --]
Get rid of semaphore abuse by converting device_driver->unload_sem semaphore to device_driver->unloaded completion.
This should get rid of any confusion as well as save a few bytes in the
process.
Signed-off-by: Mike Waychison <michael.waychison@sun.com>
---
drivers/base/bus.c | 2 +-
drivers/base/driver.c | 13 ++++++-------
include/linux/device.h | 2 +-
3 files changed, 8 insertions(+), 9 deletions(-)
Index: linux-2.6.10/drivers/base/bus.c
===================================================================
--- linux-2.6.10.orig/drivers/base/bus.c 2004-12-24 16:34:26.000000000 -0500
+++ linux-2.6.10/drivers/base/bus.c 2005-01-25 02:14:10.000000000 -0500
@@ -65,7 +65,7 @@ static struct sysfs_ops driver_sysfs_ops
static void driver_release(struct kobject * kobj)
{
struct device_driver * drv = to_driver(kobj);
- up(&drv->unload_sem);
+ complete(&drv->unloaded);
}
static struct kobj_type ktype_driver = {
Index: linux-2.6.10/drivers/base/driver.c
===================================================================
--- linux-2.6.10.orig/drivers/base/driver.c 2004-12-24 16:35:25.000000000 -0500
+++ linux-2.6.10/drivers/base/driver.c 2005-01-25 11:09:23.579643112 -0500
@@ -79,14 +79,14 @@ void put_driver(struct device_driver * d
* since most of the things we have to do deal with the bus
* structures.
*
- * The one interesting aspect is that we initialize @drv->unload_sem
- * to a locked state here. It will be unlocked when the driver
- * reference count reaches 0.
+ * The one interesting aspect is that we setup @drv->unloaded
+ * as a completion that gets complete when the driver reference
+ * count reaches 0.
*/
int driver_register(struct device_driver * drv)
{
INIT_LIST_HEAD(&drv->devices);
- init_MUTEX_LOCKED(&drv->unload_sem);
+ init_completion(&drv->unloaded);
return bus_add_driver(drv);
}
@@ -97,7 +97,7 @@ int driver_register(struct device_driver
*
* Again, we pass off most of the work to the bus-level call.
*
- * Though, once that is done, we attempt to take @drv->unload_sem.
+ * Though, once that is done, we wait until @drv->unloaded is completed.
* This will block until the driver refcount reaches 0, and it is
* released. Only modular drivers will call this function, and we
* have to guarantee that it won't complete, letting the driver
@@ -107,8 +107,7 @@ int driver_register(struct device_driver
void driver_unregister(struct device_driver * drv)
{
bus_remove_driver(drv);
- down(&drv->unload_sem);
- up(&drv->unload_sem);
+ wait_for_completion(&drv->unloaded);
}
/**
Index: linux-2.6.10/include/linux/device.h
===================================================================
--- linux-2.6.10.orig/include/linux/device.h 2004-12-24 16:35:28.000000000 -0500
+++ linux-2.6.10/include/linux/device.h 2005-01-25 02:13:13.000000000 -0500
@@ -102,7 +102,7 @@ struct device_driver {
char * name;
struct bus_type * bus;
- struct semaphore unload_sem;
+ struct completion unloaded;
struct kobject kobj;
struct list_head devices;
next prev parent reply other threads:[~2005-01-25 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 18:25 [PATCH] fix bad locking in drivers/base/driver.c Jirka Kosina
2005-01-24 19:00 ` Chris Wright
2005-01-25 5:56 ` Greg KH
2005-01-25 7:32 ` Mike Waychison
2005-01-25 13:49 ` Bill Davidsen
2005-01-25 16:10 ` Mike Waychison [this message]
2005-01-25 16:27 ` Linus Torvalds
2005-01-25 19:19 ` Greg KH
2005-01-25 19:38 ` Thomas Gleixner
2005-02-02 23:35 ` Greg KH
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=41F66F86.4000609@sun.com \
--to=michael.waychison@sun.com \
--cc=davidsen@tmr.com \
--cc=greg@kroah.com \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@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