From: Greg KH <greg@kroah.com>
To: Laurent Pinchart <laurent.pinchart@skynet.be>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-kernel@vger.kernel.org, v4l <video4linux-list@redhat.com>
Subject: Re: [BUG] cdev_put() race condition
Date: Wed, 17 Dec 2008 11:35:25 -0800 [thread overview]
Message-ID: <20081217193525.GA24916@kroah.com> (raw)
In-Reply-To: <200812172027.13771.laurent.pinchart@skynet.be>
On Wed, Dec 17, 2008 at 08:27:13PM +0100, Laurent Pinchart wrote:
> Hi Greg,
>
> On Wednesday 17 December 2008, Greg KH wrote:
> > On Wed, Dec 17, 2008 at 02:37:33PM +0100, Hans Verkuil wrote:
> > > > Again, don't use cdev's reference counting for your own object
> > > > lifecycle, it is different and will cause problems, like you have found
> > > > out.
> > >
> > > Sigh. It has nothing to do with how v4l uses it. And to demonstrate this,
> > > here is how you reproduce it with the sg module (tested it with my USB
> > > harddisk).
> > >
> > > 1) apply this patch to char_dev.c:
> >
> > <snip>
> >
> > Ok, since I can't convince you that using a cdev for your reference
> > counting is incorrect, I'll have to go change the cdev code to prevent
> > you from doing this :(
>
> Don't give up yet :-)
>
> As v4l isn't the only kernel subsystem wrongly using cdev (Hans showed that sg
> also suffered from race conditions), people seem not to understand cdev
> properly.
I totally agree, it is not the most easily understood chunk of code.
> Maybe you should start by explaining what cdev has been designed to
> handle and how to use it in device drivers (such as sg or v4l) instead
> of telling us what not to do.
As I didn't create this code, but for some reason seem to maintain it,
I'll work on creating a document to do this. But as the holidays are
rapidly approaching, it might be a while before I can get to it.
thanks,
greg k-h
next prev parent reply other threads:[~2008-12-17 19:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 20:56 [BUG] cdev_put() race condition Hans Verkuil
2008-12-16 10:06 ` Hans Verkuil
2008-12-16 20:22 ` Greg KH
2008-12-16 21:00 ` Hans Verkuil
2008-12-16 21:21 ` Greg KH
2008-12-16 23:23 ` Hans Verkuil
2008-12-16 23:30 ` Greg KH
2008-12-17 13:37 ` Hans Verkuil
2008-12-17 14:52 ` Boaz Harrosh
2008-12-17 15:07 ` Hans Verkuil
2008-12-17 16:09 ` Boaz Harrosh
2008-12-17 17:33 ` Hans Verkuil
2008-12-17 18:08 ` Al Viro
2008-12-18 8:12 ` Boaz Harrosh
2008-12-18 8:25 ` Boaz Harrosh
2008-12-17 18:16 ` Greg KH
2008-12-17 19:27 ` Laurent Pinchart
2008-12-17 19:35 ` Greg KH [this message]
2008-12-17 19:30 ` Hans Verkuil
2008-12-17 19:38 ` Greg KH
2008-12-17 19:39 ` Hans Verkuil
2008-12-17 19:53 ` Greg KH
2008-12-17 20:18 ` Hans Verkuil
2008-12-17 20: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=20081217193525.GA24916@kroah.com \
--to=greg@kroah.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@skynet.be \
--cc=linux-kernel@vger.kernel.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