From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Greg KH <greg@kroah.com>
Cc: Mike Galbraith <efault@gmx.de>, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>,
Linux and Kernel Video <video4linux-list@redhat.com>,
Linux DVB <linux-dvb@linuxtv.org>
Subject: Re: 2.6.18-rc3-mm2: oops in device_bind_driver()
Date: Mon, 14 Aug 2006 18:28:54 -0300 [thread overview]
Message-ID: <1155590934.13789.19.camel@praia> (raw)
In-Reply-To: <20060814210308.GH11673@kroah.com>
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.
For sure some newer locks will be required for multithread probe.
>
> thanks,
>
> greg k-h
Cheers,
Mauro.
next prev parent reply other threads:[~2006-08-14 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-12 12:28 2.6.18-rc3-mm2: oops in device_bind_driver() Mike Galbraith
2006-08-13 1:02 ` Andrew Morton
2006-08-13 5:50 ` Mike Galbraith
2006-08-14 21:03 ` Greg KH
2006-08-14 21:28 ` Mauro Carvalho Chehab [this message]
2006-08-14 23:52 ` Greg KH
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=1155590934.13789.19.camel@praia \
--to=mchehab@infradead.org \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=greg@kroah.com \
--cc=linux-dvb@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=video4linux-list@redhat.com \
/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