From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Andrew Morton <akpm@osdl.org>,
ALSA development <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>, Greg KH <gregkh@suse.de>,
LKML <linux-kernel@vger.kernel.org>, Jiri Kosina <jikos@jikos.cz>,
Castet Matthieu <castet.matthieu@free.fr>
Subject: Re: [Alsa-devel] [PATCH] Driver core: Don't ignore error returns from probing
Date: Fri, 6 Oct 2006 13:14:43 +0200 [thread overview]
Message-ID: <20061006131443.473c203c@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0610061138580.8573@tm8103.perex-int.cz>
On Fri, 6 Oct 2006 11:41:05 +0200 (CEST),
Jaroslav Kysela <perex@suse.cz> wrote:
> > Hm, I don't think we should call device_release_driver if
> > bus_attach_device failed (and I think calling bus_remove_device if
> > bus_attach_device failed is unintuitive). I did a patch that added a
> > function which undid just the things bus_add_device did (here:
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=115816560424389&w=2),
> > which unfortunately got lost somewhere... (I'll rebase and resend.)
>
> Yes, but it might be better to check dev->is_registered flag in
> bus_remove_device() before device_release_driver() call to save some code,
> rather than reuse most of code in bus_delete_device().
If we undid things (symlinks et al.) in the order we added them, we can
factor out bus_delete_device() from bus_remove_device() and avoid both
code duplication and calling bus_remove_device() if bus_attach_device()
failed. Something like the patch below (untested).
--- linux-2.6-CH.orig/drivers/base/base.h
+++ linux-2.6-CH/drivers/base/base.h
@@ -17,6 +17,7 @@ extern int attribute_container_init(void
extern int bus_add_device(struct device * dev);
extern int bus_attach_device(struct device * dev);
+extern void bus_delete_device(struct device * dev);
extern void bus_remove_device(struct device * dev);
extern struct bus_type *get_bus(struct bus_type * bus);
extern void put_bus(struct bus_type * bus);
--- linux-2.6-CH.orig/drivers/base/bus.c
+++ linux-2.6-CH/drivers/base/bus.c
@@ -360,7 +360,7 @@ static void device_remove_attrs(struct b
* bus_add_device - add device to bus
* @dev: device being added
*
- * - Add the device to its bus's list of devices.
+ * - Add attributes.
* - Create link to device's bus.
*/
int bus_add_device(struct device * dev)
@@ -424,29 +424,44 @@ int bus_attach_device(struct device * de
}
/**
- * bus_remove_device - remove device from bus
- * @dev: device to be removed
+ * bus_delete_device - undo bus_add_device
+ * @dev: device being deleted
*
- * - Remove symlink from bus's directory.
- * - Delete device from bus's list.
- * - Detach from its driver.
- * - Drop reference taken in bus_add_device().
+ * - Remove symlink from bus's directory.
+ * - Remove attributes.
+ * - Drop reference taken in bus_add_device().
*/
-void bus_remove_device(struct device * dev)
+void bus_delete_device(struct device * dev)
{
if (dev->bus) {
sysfs_remove_link(&dev->kobj, "subsystem");
sysfs_remove_link(&dev->kobj, "bus");
sysfs_remove_link(&dev->bus->devices.kobj, dev->bus_id);
device_remove_attrs(dev->bus, dev);
- dev->is_registered = 0;
- klist_del(&dev->knode_bus);
- pr_debug("bus %s: remove device %s\n", dev->bus->name, dev->bus_id);
- device_release_driver(dev);
put_bus(dev->bus);
}
}
+/**
+ * bus_remove_device - remove device from bus
+ * @dev: device to be removed
+ *
+ * - Remove symlink from bus's directory.
+ * - Delete device from bus's list.
+ * - Detach from its driver.
+ * - Drop reference taken in bus_add_device().
+ */
+void bus_remove_device(struct device * dev)
+{
+ if (!dev->bus)
+ return;
+ dev->is_registered = 0;
+ klist_del(&dev->knode_bus);
+ pr_debug("bus %s: remove device %s\n", dev->bus->name, dev->bus_id);
+ device_release_driver(dev);
+ bus_delete_device(dev);
+}
+
static int driver_add_attrs(struct bus_type * bus, struct device_driver * drv)
{
int error = 0;
--- linux-2.6-CH.orig/drivers/base/core.c
+++ linux-2.6-CH/drivers/base/core.c
@@ -479,7 +479,9 @@ int device_add(struct device *dev)
if ((error = bus_add_device(dev)))
goto BusError;
kobject_uevent(&dev->kobj, KOBJ_ADD);
- bus_attach_device(dev);
+ error = bus_attach_device(dev);
+ if (error)
+ goto attachError;
if (parent)
klist_add_tail(&dev->knode_parent, &parent->klist_children);
@@ -498,6 +500,8 @@ int device_add(struct device *dev)
kfree(class_name);
put_device(dev);
return error;
+ attachError:
+ bus_delete_device(dev);
BusError:
device_pm_remove(dev);
PMError:
next prev parent reply other threads:[~2006-10-06 11:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 20:22 [PATCH] ALSA: fix kernel panic in initialization of mpu401 driver Jiri Kosina
2006-10-05 8:07 ` Jaroslav Kysela
2006-10-05 9:57 ` Jiri Kosina
2006-10-05 14:02 ` Alan Stern
2006-10-05 14:16 ` Jaroslav Kysela
2006-10-05 17:58 ` Greg KH
2006-10-05 21:03 ` [PATCH] Driver core: Don't ignore error returns from probing Alan Stern
2006-10-06 7:53 ` Cornelia Huck
2006-10-06 7:57 ` [PATCH] driver core: bus_attach_device() retval check Cornelia Huck
2006-10-06 9:41 ` [Alsa-devel] [PATCH] Driver core: Don't ignore error returns from probing Jaroslav Kysela
2006-10-06 11:14 ` Cornelia Huck [this message]
2006-10-06 11:46 ` Jaroslav Kysela
2006-10-06 18:12 ` Alan Stern
2006-10-09 11:10 ` Cornelia Huck
2006-10-09 11:14 ` [PATCH] Driver core: Don't ignore bus_attach_device() retval Cornelia Huck
2006-10-09 14:10 ` Alan Stern
2006-10-11 14:49 ` Alan Stern
2006-10-12 9:30 ` Cornelia Huck
2006-10-12 15:59 ` Alan Stern
2006-10-12 17:17 ` Cornelia Huck
2006-10-12 21:41 ` Alan Stern
2006-10-13 6:37 ` Cornelia Huck
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=20061006131443.473c203c@gondolin.boeblingen.de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=castet.matthieu@free.fr \
--cc=gregkh@suse.de \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=stern@rowland.harvard.edu \
--cc=tiwai@suse.de \
/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®