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: <6006da6281d43f4f5a55dd6434d40eedfc7ae4fd.camel@sipsolutions.net>
Date: Thu, 05 Feb 2026 09:17:59 +0100
From: Johannes Berg <johannes@...solutions.net>
To: "Loktionov, Aleksandr" <aleksandr.loktionov@...el.com>, Ethan
 Nelson-Moore <enelsonmoore@...il.com>, "netdev@...r.kernel.org"
 <netdev@...r.kernel.org>,  "linux-wireless@...r.kernel.org"	
 <linux-wireless@...r.kernel.org>
Cc: "stable@...r.kernel.org" <stable@...r.kernel.org>, "Nguyen, Anthony L"	
 <anthony.l.nguyen@...el.com>, "Kitszel, Przemyslaw"	
 <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>
Subject: Re: [PATCH net-next] net: intel: fix PCI device ID conflict between
 i40e and ipw2200

On Thu, 2026-02-05 at 08:13 +0000, Loktionov, Aleksandr wrote:
> > 
> Commit message could be more detailed.
> - Why the PCI ID is being reused (if known) Is this actually a reuse after EOL, or is there a misunderstanding? The commit message hand-waves this critical detail.

Well, if you and I can't figure this out internally to Intel, I doubt
anyone _else_ can. Sure, ipw2200 is EOL for *long*, but Intel still
shouldn't have reused the IDs even if the old ones got carried forward
from PCI to PCIe.

> - Whether this is documented in hardware datasheets

Good luck finding any documentation on ipw2200 these days. Those devices
shipped 20+ years ago.

> - If there are bug reports of the conflict in the wild

Does it matter? If you have a system with either of those, you'll get
lucky if it works, and get a mess if it doesn't. ipw2200 driver will
probably bind to just about any device with the right IDs since it
doesn't do much in probe().

johannes