From: Greg KH <greg@kroah.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Tejun Heo <tj@home-tj.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.10-rc1 2/5] driver-model: bus_recan_devices() locking fix
Date: Mon, 15 Nov 2004 21:52:24 -0800 [thread overview]
Message-ID: <20041116055224.GF29328@kroah.com> (raw)
In-Reply-To: <200411092317.33300.dtor_core@ameritech.net>
On Tue, Nov 09, 2004 at 11:17:31PM -0500, Dmitry Torokhov wrote:
> On Tuesday 09 November 2004 07:40 pm, Greg KH wrote:
> > > I think we just have lay down the rules that one needs to get a reference
> > > to an object in the following cases:
> > > - object creation (first reference)
> > > - linking some other object to the object in question. Every link to the
> > > ? object should increase reference count.
> > > - before passing object to another thread of execution to guarantee that
> > > ? the object will live long enough for both threads.
> >
> > The rules are defined. ?See my OLS 2004 paper on krefs for details.
> >
>
> So that means you will patches like the one below, right?
>
> diff -Nru a/drivers/base/driver.c b/drivers/base/driver.c
> --- a/drivers/base/driver.c 2004-11-09 23:16:43 -05:00
> +++ b/drivers/base/driver.c 2004-11-09 23:16:43 -05:00
> @@ -26,13 +26,7 @@
>
> int driver_create_file(struct device_driver * drv, struct driver_attribute * attr)
> {
> - int error;
> - if (get_driver(drv)) {
> - error = sysfs_create_file(&drv->kobj, &attr->attr);
> - put_driver(drv);
> - } else
> - error = -EINVAL;
> - return error;
> + return sysfs_create_file(&drv->kobj, &attr->attr);
> }
>
>
> @@ -44,10 +38,7 @@
>
> void driver_remove_file(struct device_driver * drv, struct driver_attribute * attr)
> {
> - if (get_driver(drv)) {
> - sysfs_remove_file(&drv->kobj, &attr->attr);
> - put_driver(drv);
> - }
> + sysfs_remove_file(&drv->kobj, &attr->attr);
> }
While not totally necessary, the current code is safe :)
I'll ask Pat about this next time I see him.
thanks,
greg k-h
next prev parent reply other threads:[~2004-11-16 5:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 7:01 [PATCH 2.6.10-rc1 0/5] driver-model: misc bug fixes Tejun Heo
2004-11-04 7:02 ` [PATCH 2.6.10-rc1 1/5] driver-model: comment fix in bus.c Tejun Heo
2004-11-04 18:35 ` Greg KH
2004-11-04 7:02 ` [PATCH 2.6.10-rc1 2/5] driver-model: bus_recan_devices() locking fix Tejun Heo
2004-11-04 18:58 ` Greg KH
2004-11-04 19:12 ` Dmitry Torokhov
2004-11-05 6:14 ` Tejun Heo
2004-11-05 16:33 ` Dmitry Torokhov
2004-11-09 1:27 ` Tejun Heo
2004-11-09 1:43 ` Dmitry Torokhov
2004-11-10 7:13 ` Tejun Heo
2004-11-10 0:40 ` Greg KH
2004-11-10 4:17 ` Dmitry Torokhov
2004-11-16 5:52 ` Greg KH [this message]
2004-11-04 7:03 ` [PATCH 2.6.10-rc1 3/5] driver-model: sysfs_release() dangling pointer reference fix Tejun Heo
2004-11-04 18:59 ` Greg KH
2004-11-04 7:04 ` [PATCH 2.6.10-rc1 4/5] driver-model: kobject_add() error path reference counting fix Tejun Heo
2004-11-04 19:00 ` Greg KH
2004-11-04 7:05 ` [PATCH 2.6.10-rc1 5/5] driver-model: device_add() " Tejun Heo
2004-11-04 20:07 ` 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=20041116055224.GF29328@kroah.com \
--to=greg@kroah.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@home-tj.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.