linux-kernel - Re: staging driver s626 clashes with philips SAA7146 media/dvb based cards

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:	Tue, 16 Jun 2009 13:51:21 -0700
From:	Greg KH <gregkh@...e.de>
To:	Herton Ronaldo Krzesinski <herton@...driva.com.br>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Gianluca Palli <gpalli@...s.unibo.it>,
	David Schleef <ds@...leef.org>,
	Frank Mori Hess <fmhess@...rs.sourceforge.net>,
	Ian Abbott <abbotti@....co.uk>
Subject: Re: staging driver s626 clashes with philips SAA7146 media/dvb
	based cards

On Tue, Jun 16, 2009 at 05:01:44PM -0300, Herton Ronaldo Krzesinski wrote:
> Hi,
> 
> The s626 (comedi) driver in staging conflicts with philips SAA7146 media/dvb
> based cards, because it claims the same vendor:device pci id for all 
> subdevice/subvendor ids. What happens is that for people that have a philips 
> SAA7146 based card, s626 if available gets loaded by udev and makes system 
> freeze (https://qa.mandriva.com/show_bug.cgi?id=51445).

So a PCI device that does different things has the same device ids?
ick, stupid vendors...

> Looks like s626 shouldn't claim all 1131:7146 devices, either by specifying 
> specific subdevice/subvendor ids specific to s626 devices or doing additional 
> checks in its probe/attach function.

If you can propose the proper sub ids, or the needed checks, please send
a patch.

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/