netdev - PCI ID 10ec:8129 is in both 8139too and r8169

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-next>] [day] [month] [year] [list]

Message-ID: <CADkSEUjsT8OW9QVa-U4PQMG+8c1tjjxk7tNJu3U+6yoC82Y7FQ@mail.gmail.com>
Date: Tue, 3 Feb 2026 23:47:17 -0800
From: Ethan Nelson-Moore <enelsonmoore@...il.com>
To: netdev@...r.kernel.org
Cc: Heiner Kallweit <hkallweit1@...il.com>, nic_swsd@...ltek.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>
Subject: PCI ID 10ec:8129 is in both 8139too and r8169

This doesn't seem right - 10ec:8129 is the RTL8129 which is much older.

It was added to r8169 in commit
de1e938e54deba5b093a3074dfafd0d11afacbe1, which said that RTL8110SBL
uses it. Can anyone at Realtek confirm or deny this? The device ID
should not be in more than one driver, because in that case, which
driver is used is unpredictable.

It might have been an unprogrammed device, since I have heard
elsewhere that newer devices with no EEPROM can appear as 10ec:8129
(in which case they don't work).

Ethan