From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756502AbYIIIFB (ORCPT ); Tue, 9 Sep 2008 04:05:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754313AbYIIIEp (ORCPT ); Tue, 9 Sep 2008 04:04:45 -0400 Received: from casper.infradead.org ([85.118.1.10]:55800 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754010AbYIIIEo (ORCPT ); Tue, 9 Sep 2008 04:04:44 -0400 Date: Tue, 9 Sep 2008 01:04:03 -0700 From: Greg KH To: Steve Calfee Cc: Matthew Wilcox , Alan Stern , USB list , bgmerrell@novell.com, hirofuchi@users.sourceforge.net, Kernel development list , usbip-devel@lists.sourceforge.net Subject: Re: USBIP protocol Message-ID: <20080909080403.GA12614@kroah.com> References: <20080904214802.GO2772@parisc-linux.org> <20080909005353.GR2772@parisc-linux.org> <4a5ff6bc0809090012j7121108cpc4cf108a4c323c52@mail.gmail.com> <20080909073356.GA12284@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080909073356.GA12284@kroah.com> User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.