Re: USBIP protocol

From: Greg KH
Date: Tue Sep 09 2008 - 04:05:01 EST

On Tue, Sep 09, 2008 at 12:33:56AM -0700, Greg KH wrote:
> On Tue, Sep 09, 2008 at 12:12:37AM -0700, Steve Calfee wrote:
> >
> > My problem is I am using the latest Suse enterprise linux which uses
> > kernel 2.6.18
> Actually it's 2.6.16 "based" with over 2000 patches added to it :)
> > ..... In that kernel the probes are done by the device
> > system and if a modprobe definition says the module is for this device
> > it gets loaded (by udev I think) and probed. fine. If the module is
> > already loaded the kernel probes the modules in the order they were
> > insmoded (if they say they want the particular VID/PID/CLASS/wildcard
> > etc.)
> >
> > The problem is the probing is done by the kernel driver stuff and the
> > insmoding and user space intelligence is done by udev. Once a kernel
> > module is installed it must take all devices that match it's device ID
> > table. Remember USBIP matches everything! That is because (at least
> > in the 2.6.18 kernel) the kernel driver stuff stops probing after a
> > probe fails.
> No it doesn't, it continues on. Or it should. Perhaps it's been fixed
> since then, I would rely on that kernel to be looking like anything
^ not

> "real" these days, it is very old and only supported by Novell, and not
> the target audience for this patch at all.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at