mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: linux-usb-devel@lists.sourceforge.net
Cc: Pavel Machek <pavel@suse.cz>, Andrew Morton <akpm@osdl.org>,
	Greg KH <greg@kroah.com>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] 2.6.20-rc4: null pointer deref in khubd
Date: Thu, 11 Jan 2007 14:21:47 +0100	[thread overview]
Message-ID: <200701111421.48125.oliver@neukum.org> (raw)
In-Reply-To: <20070110203809.GA6378@ucw.cz>

Am Mittwoch, 10. Januar 2007 21:38 schrieb Pavel Machek:
> Hi!
> 
> > > usb 2-1: new full speed USB device using uhci_hcd and address 68
> > > usb 2-1: USB disconnect, address 68
> > > usb 2-1: unable to read config index 0 descriptor/start
> > > usb 2-1: chopping to 0 config(s)
> > 
> > Does anybody know a legitimate reasons a device should have
> > 0 configurations? Independent of the reason of this bug, should we disallow
> > such devices and error out?
> 
> It is not bad device, btw, but extremely flakey connector. Bug is
> random :-(, and machine is smp, so it might even be a race.

With that config option, there's a race even on UP. probe() can
sleep.

	Regards
		Oliver

      reply	other threads:[~2007-01-11 13:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-10 10:49 Pavel Machek
2007-01-10 15:49 ` Oliver Neukum
2007-01-10 16:14   ` [linux-usb-devel] " Alan Stern
2007-01-10 17:01     ` Oliver Neukum
2007-01-10 17:31       ` Alan Stern
2007-01-10 19:54         ` Oliver Neukum
2007-01-10 22:35           ` Alan Stern
2007-01-10 22:56             ` Pavel Machek
2007-01-11  7:48             ` Oliver Neukum
2007-01-11 10:34               ` Pavel Machek
2007-01-11 13:08                 ` Oliver Neukum
2007-01-10 20:38   ` Pavel Machek
2007-01-11 13:21     ` Oliver Neukum [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=200701111421.48125.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=pavel@suse.cz \
    /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

Powered by JetHome