public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stelian Pop <stelian@popies.net>, hare@suse.de
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] usb sysfs intf files no longer created when probe fails
Date: Wed, 22 Jun 2005 09:17:36 -0700	[thread overview]
Message-ID: <20050622161735.GA2274@kroah.com> (raw)
In-Reply-To: <1119452190.4794.6.camel@localhost.localdomain>

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

  parent reply	other threads:[~2005-06-22 16:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22 13:50 usb sysfs intf files no longer created when probe fails Stelian Pop
2005-06-22 14:07 ` [linux-usb-devel] " Stelian Pop
2005-06-22 14:56   ` Stelian Pop
2005-06-22 16:03     ` Alan Stern
2005-06-22 18:33       ` Stelian Pop
2005-06-22 16:17     ` Greg KH [this message]
2005-06-22 14:59 ` Greg KH
2005-06-22 15:09   ` [linux-usb-devel] " Stelian Pop
2005-06-22 15:41     ` Alan Stern
2005-06-22 15:53       ` Stelian Pop
2005-06-22 16:22         ` Greg KH
2005-06-22 18:27           ` Stelian Pop
2005-06-22 16:26         ` Greg KH
2005-06-22 18:25           ` Stelian Pop

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=20050622161735.GA2274@kroah.com \
    --to=greg@kroah.com \
    --cc=hare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stelian@popies.net \
    /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