linux-kernel - Re: [BUG] cdev_put() race condition

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 17 Dec 2008 12:52:49 -0800
From:	Greg KH <greg@...ah.com>
To:	Hans Verkuil <hverkuil@...all.nl>
Cc:	video4linux-list@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [BUG] cdev_put() race condition

On Wed, Dec 17, 2008 at 09:18:29PM +0100, Hans Verkuil wrote:
> On Wednesday 17 December 2008 20:53:29 Greg KH wrote:
> > So why is V4L different than the rest of the kernel in that it wishes to
> > do things differently?
> 
> Because it has almost no proper framework to speak of and what little there 
> is has been pretty much unchanged since the very beginning.

Ick.

> I'm trying to develop a decent framework that should help support upcoming 
> devices and generally make life easier for v4l driver developers.
> 
> And I've no idea why we don't just use the device's release() callback for 
> this. I'm going to implement this right now :-)

Thanks, that makes oh so much more sense.  Let me know when you've
completed it so I can make your cdev change as well.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/