linux-kernel - 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 for Android: free password hash cracker in your pocket

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

Message-Id: <200906161701.45234.herton@mandriva.com.br>
Date:	Tue, 16 Jun 2009 17:01:44 -0300
From:	Herton Ronaldo Krzesinski <herton@...driva.com.br>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Greg KH <gregkh@...e.de>, Gianluca Palli <gpalli@...s.unibo.it>,
	David Schleef <ds@...leef.org>,
	Frank Mori Hess <fmhess@...rs.sourceforge.net>,
	Ian Abbott <abbotti@....co.uk>
Subject: staging driver s626 clashes with philips SAA7146 media/dvb based cards

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).

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.

--
[]'s
Herton
--
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/