Re: [linux-usb-devel] usb sysfs intf files no longer created when probe fails
From: Greg KH
Date: Wed Jun 22 2005 - 11:26:07 EST
On Wed, Jun 22, 2005 at 04:56:30PM +0200, Stelian Pop wrote:
> Le mercredi 22 juin 2005 ?? 16:07 +0200, Stelian Pop a ??crit :
> > Le mercredi 22 juin 2005 ?? 15:50 +0200, Stelian Pop a ??crit :
> >
> > > I use the 'atp' input driver from http://popies.net/atp/ to drive this
> > > touchpad. When removing the driver I also get an oops, possibly related
> > > to the previous failure to create the sysfs file:
>
> Ok, there are two separate problems here:
>
> 1. The sysfs intf entry is not created, and this causes the oops later
> when trying to remove the entry, etc.
>
> I've tracked this problem back to this patch:
> [PATCH] driver core: fix error handling in bus_add_device
> http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ca2b94ba12f3c36fd3d6ed9d38b3798d4dad0d8b
>
> Once the patch above is reverted, I have no more oops, my driver can
> be loaded/unloaded just fine, and the /sys/devices/.../ is present.
Thanks for tracking this down.
Hm, we must be actually checking the return value somewhere, and dying
because of it. Let me dig deeper and find out.
Oh, can you enable debugging for the driver core (it's a config option)
and the USB core and without that patch reverted, let me know what the
syslog shows when the probe fails?
> However, I'm not really sure if the problem comes from the above
> patch or from my driver which should manually call
> usb_create_sysfs_intf_files() or something equivalent.
No, you should not have to call that from your driver. In looking at
your code, I don't see anything obviously wrong. It works just fine
with 2.6.12, right?
> 2. There is still a problem with the early loading of the driver. If
> loaded at boot, it won't work. If I rmmod/insmod it later it does.
Does that also work with 2.6.12?
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/