Re: 2.6.18-rc3-mm2: oops in device_bind_driver()

[Greg KH <greg@kroah.com>]

On Mon, Aug 14, 2006 at 06:28:54PM -0300, Mauro Carvalho Chehab wrote:
> Em Seg, 2006-08-14 ?s 14:03 -0700, Greg KH escreveu:
> > On Sun, Aug 13, 2006 at 05:50:34AM +0000, Mike Galbraith wrote:
> > > On Sat, 2006-08-12 at 18:02 -0700, Andrew Morton wrote:
> > > 
> > > > I'd assume that you have CONFIG_PCI_MULTITHREAD_PROBE set, and
> > > 
> > > Yes.
> > 
> > Mauro, this is odd.  Anything in the dvb layer that would not like
> > multiple devices being probed at the same time?
> We should hardly check for all race conditions. It is likely to cause
> some random troubles at both V4L and DVB sides. 
> 
> For example, on V4L side, this may produce weird stuff like bad device
> number associations (for example, the same device might get /dev/video0
> and /dev/radio1, but apps expects to have the same numbering for
> both)...
> 
> The same on DVB: demux0 should be associated with frontend0, for DVB to
> work properly, but, with simultaneous probing, this might not happen.

How do you prevent this from happening today, with USB devices showing
up at any point in time, combined with PCI hotplug devices?

> For sure some newer locks will be required for multithread probe.

I think you need it even without this PCI change :)

thanks,

greg k-h