Re: Delayed hotplug events

[Greg KH <greg@kroah.com>]

On Thu, Jun 17, 2004 at 04:29:20PM -0700, Patrick Mansfield wrote:
> On Thu, Jun 17, 2004 at 11:09:30AM -0700, Greg KH wrote:
> > On Thu, Jun 17, 2004 at 01:21:48PM +0200, Hannes Reinecke wrote:
> 
> > > As an example of how it should be used I've patched 
> > > drivers/scsi/scsi_sysfs.c:scsi_sysfs_add_sdev(), so that the device 
> > > "add" event will now be triggered only _after_ the device has been 
> > > initialised properly, including all sysfs attributes.
> > > 
> > > Is this approach feasible or am I completely off kilter here?
> > 
> > Off kilter :)
> > 
> > > And if the latter, how should it be solved properly?
> > 
> > In userspace, with things like udevd and just simply sleeping for a
> > short ammount of time to allow the kernel to catch up to userspace :)
> 
> I thought you were going to fix this in 2.7, or do you mean for 2.6, fix
> it in userspace?

Yes, for 2.6 do it in userspace.  For 2.7, I'm going to revisit this to
try to keep this from happening.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
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