From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965044AbWHQPq3 (ORCPT ); Thu, 17 Aug 2006 11:46:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965047AbWHQPq2 (ORCPT ); Thu, 17 Aug 2006 11:46:28 -0400 Received: from mail.kroah.org ([69.55.234.183]:30156 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S965044AbWHQPq1 (ORCPT ); Thu, 17 Aug 2006 11:46:27 -0400 Date: Thu, 17 Aug 2006 08:42:45 -0700 From: Greg KH To: Olaf Hering Cc: Benjamin Herrenschmidt , Alan Cox , akpm@osdl.org, linux-kernel@vger.kernel.org Subject: Re: PATCH: Multiprobe sanitizer Message-ID: <20060817154245.GB7070@kroah.com> References: <1155746538.24077.371.camel@localhost.localdomain> <20060816222633.GA6829@kroah.com> <1155774994.15195.12.camel@localhost.localdomain> <1155797833.11312.160.camel@localhost.localdomain> <1155804060.15195.30.camel@localhost.localdomain> <1155806676.11312.175.camel@localhost.localdomain> <20060817120013.GC6843@kroah.com> <1155816777.11312.177.camel@localhost.localdomain> <20060817122244.GA17956@kroah.com> <20060817144329.GA20790@aepfle.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060817144329.GA20790@aepfle.de> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 17, 2006 at 04:43:29PM +0200, Olaf Hering wrote: > On Thu, Aug 17, 2006 at 05:22:44AM -0700, Greg KH wrote: > > On Thu, Aug 17, 2006 at 02:12:57PM +0200, Benjamin Herrenschmidt wrote: > > > On Thu, 2006-08-17 at 05:00 -0700, Greg KH wrote: > > > > On Thu, Aug 17, 2006 at 11:24:35AM +0200, Benjamin Herrenschmidt wrote: > > > > > Probe ordering is fragile and completely defeated with busses that are > > > > > already probed asynchronously (like USB or firewire), and things can > > > > > only get worse. Thus we need to look for generic solutions, the trick of > > > > > maintaining probe ordering will work around problems today but we'll > > > > > still hit the wall in an increasing number of cases in the future. > > > > > > > > That's exactly why udev was created :) > > > > > > > > It can handle bus ordering issues already today just fine, and distros > > > > use it this way in shipping, "enterprise ready" products. > > > > > > Only up to a certain point and for certain drivers... but yeah. > > > > What drivers are not supported by this? Seriously, have we missed any? > > Do serial drivers have a device symlink now Yes: $ tree /sys/class/tty/ttyS0 /sys/class/tty/ttyS0 |-- dev |-- device -> ../../../devices/platform/serial8250 |-- subsystem -> ../../../class/tty `-- uevent > and video drivers? Properly written ones do, I have heard reports that some do not, but that's a driver bug that should be fixed with a one line addition. If you know of any specific ones, please let me know and I'll make the needed change. thanks, greg k-h