mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Greg K-H <greg@kroah.com>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2/9] driver core fixes: device_register() retval check in platform.c
Date: Mon, 25 Sep 2006 16:58:30 +0200	[thread overview]
Message-ID: <20060925165830.0bcdce55@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20060923211032.GA4363@flint.arm.linux.org.uk>

On Sat, 23 Sep 2006 22:10:32 +0100,
Russell King <rmk+lkml@arm.linux.org.uk> wrote:

> I don't think there's much value in patches such as this - if the
> platform bus type didn't register, what happens when we then try
> to register a platform device driver or a platform device?  ISTR
> doing that before the bus type is registered leads to an OOPS.

Yes, since the klists have not yet been initialized.

> So, presumably to do this properly, if the platform_bus_type failed
> to register, you need to force all platform device/platform device
> driver registrations to also fail.

We should fail registration (gracefully) of all devices/drivers which
specify a bus that is !NULL but has not been registered. Unfortunately,
I don't see an easy way to do this.

However, we can fail the registration of devices that specify a parent
that is !NULL but not yet added to the tree. This catches platform
devices registering before platform_bus_type (since platform_bus is not
registered then), similar for other bus types like iucv.
(Unfortunately, not drivers...)


From: Cornelia Huck <cornelia.huck@de.ibm.com>

Force parent devices to be registered before their children. Otherwise we'll
oops when creating the child's sysfs directory.

Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>

---
 drivers/base/bus.c  |    6 ++++--
 drivers/base/core.c |    5 ++++-
 2 files changed, 8 insertions(+), 3 deletions(-)

--- linux-2.6.18-mm1.orig/drivers/base/core.c
+++ linux-2.6.18-mm1/drivers/base/core.c
@@ -474,7 +474,10 @@ int device_add(struct device *dev)
 	}
 
 	parent = get_device(dev->parent);
-
+	if (parent && !device_is_registered(parent)) {
+		error = -EINVAL;
+		goto Error;
+	}
 	pr_debug("DEV: registering device: ID = '%s'\n", dev->bus_id);
 
 	/* first, register with generic layer. */
--- linux-2.6.18-mm1.orig/drivers/base/bus.c
+++ linux-2.6.18-mm1/drivers/base/bus.c
@@ -418,7 +418,8 @@ int bus_attach_device(struct device * de
 			ret = 0;
 		} else
 			dev->is_registered = 0;
-	}
+	} else
+		dev->is_registered = 1;
 	return ret;
 }
 
@@ -443,7 +444,8 @@ void bus_remove_device(struct device * d
 		pr_debug("bus %s: remove device %s\n", dev->bus->name, dev->bus_id);
 		device_release_driver(dev);
 		put_bus(dev->bus);
-	}
+	} else
+		dev->is_registered = 0;
 }
 
 static int driver_add_attrs(struct bus_type * bus, struct device_driver * drv)

      reply	other threads:[~2006-09-25 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22  9:36 Cornelia Huck
2006-09-23 21:10 ` Russell King
2006-09-25 14:58   ` Cornelia Huck [this message]

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=20060925165830.0bcdce55@gondolin.boeblingen.de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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®