linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Kagan <rkagan@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-usb-devel] usb-storage bug in 2.6.12-rc3
Date: Fri, 29 Apr 2005 18:23:36 +0000	[thread overview]
Message-ID: <20050429182335.GC2226@katya> (raw)
In-Reply-To: <1114633284.16803.17.camel@daxter.boston.redhat.com>

On Wed, Apr 27, 2005 at 04:14:08PM -0700, Patrick Mansfield wrote:
> On Wed, Apr 27, 2005 at 05:21:10PM -0400, Alan Stern wrote:
> 
> > David's right.  Why did kobject_hotplug() move out of kobject_add() and
> > into its callers sometime after 2.6.11?  In particular the invocation in 
> > device_add() is in the wrong place; it needs to come before 
> > bus_add_device() starts probing for drivers.  Otherwise, as David points 
> > out, when the drivers start registering child devices from their probe 
> > methods, the hotplug events for those child devices will appear before the 
> > event for the parent.
> 
> But bus_add_device() calls device_add_attrs() to create attrs, if you call
> it after the hotplug, the user space hotplug event shows up before the
> sysfs attrs are created (if the driver is using the bus->dev_attrs field).

Do I get it right that at hotplug time the attributes do already exist,
but it is the sysfs files which don't?  It's certainly true for USB, I'm
much less acquainted with other subsystems.

Then, instead of trying to make sure the attributes are available via
sysfs at hotplug time, we can use another means to pass them to hotplug:
we can add a routine, which, when called from the .hotplug function
and given pointers to struct attribute and struct device, would add
environment variable

SYSFS_attrName=attrValue

using attribute's .name and .show, to the list of env variables exported
to the hotplug callout.  This would allow udev or whatever is called to
get most relevant attributes via environment, if available, otherwise to
poke in sysfs and wait until they show up.

Sorry but I can't illustrate it with a patch at the moment as I'm
leaving for four days off, maybe I'll be able to do it when I'm back.

Cheers,
  Roman.


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r 
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2005-04-29 18:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27 20:21 usb-storage bug in 2.6.12-rc3 David Zeuthen
2005-04-27 21:21 ` [linux-usb-devel] " Alan Stern
2005-04-27 23:14 ` Patrick Mansfield
2005-04-28  0:47 ` Kay Sievers
2005-04-28  4:34 ` Greg KH
2005-04-28 10:21 ` Kay Sievers
2005-04-28 13:35 ` E. Oltmanns
2005-04-28 14:15 ` Patrick Mansfield
2005-04-29 14:23 ` E. Oltmanns
2005-04-29 18:23 ` Roman Kagan [this message]
2005-04-29 19:28 ` [linux-usb-devel] " David Brownell
2005-04-29 19:35 ` Oliver Neukum
2005-04-29 20:00 ` Greg KH
2005-04-29 20:01 ` Greg KH
2005-04-29 20:16 ` Oliver Neukum
2005-04-29 20:50 ` David Brownell
2005-04-29 21:07 ` David Zeuthen
2005-05-04  7:05 ` Roman Kagan
2005-05-18 14:19 ` David Zeuthen
2005-05-18 17:03 ` 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=20050429182335.GC2226@katya \
    --to=rkagan@mail.ru \
    --cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).