netdev - Re: [PATCH net-next] net: intel: fix PCI device ID conflict between i40e and ipw2200

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]

Message-ID: <b7a1e57d6bfde3ea5c9204323341a74325a63ab8.camel@sipsolutions.net>
Date: Thu, 05 Feb 2026 09:13:25 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Ethan Nelson-Moore <enelsonmoore@...il.com>, netdev@...r.kernel.org, 
	linux-wireless@...r.kernel.org
Cc: stable@...r.kernel.org, Tony Nguyen <anthony.l.nguyen@...el.com>, 
 Przemek Kitszel <przemyslaw.kitszel@...el.com>, Andrew Lunn
 <andrew+netdev@...n.ch>, "David S. Miller"	 <davem@...emloft.net>, Eric
 Dumazet <edumazet@...gle.com>, Jakub Kicinski	 <kuba@...nel.org>, Paolo
 Abeni <pabeni@...hat.com>, Stanislav Yakovlev	 <stas.yakovlev@...il.com>,
 Alice Michael <alice.michael@...el.com>,  Aleksandr Loktionov
 <aleksandr.loktionov@...el.com>
Subject: Re: [PATCH net-next] net: intel: fix PCI device ID conflict between
 i40e and ipw2200

On Wed, 2026-02-04 at 23:54 -0800, Ethan Nelson-Moore wrote:
> The ID 8086:104f is matched by both i40e and ipw2200. The same device
> ID should not be in more than one driver, because in that case, which
> driver is used is unpredictable. Fix this by taking advantage of the
> fact that i40e devices use PCI_CLASS_NETWORK_ETHERNET and ipw2200
> devices use PCI_CLASS_NETWORK_OTHER to differentiate the devices.

Right, good solution. How did you figure out that ipw2200 uses OTHER?
I'd thought about this but was afraid it'd also just use ETHERNET.

Acked-by: Johannes Berg <johannes@...solutions.net>

(FWIW, I've found the database internally, but not who maintains it nor
any historic information in it ... still digging I guess, if only to
avoid this happening again in the future)

johannes