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: <6ae5e229-c440-4522-a9d9-7581a7e0ce1b@gmx.de>
Date: Sun, 23 Feb 2025 01:57:32 +0100
From: Michael Pflüger <empx@....de>
To: sashal@...nel.org
Cc: davem@...emloft.net, edumazet@...gle.com, hkallweit1@...il.com,
 kuba@...nel.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
 nic_swsd@...ltek.com, pabeni@...hat.com, stable@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 6.10 03/27] r8169: remove detection of chip
 version 11 (early RTL8168b)

 > Indeed, I ended up dropping from the wrong local branch yesterday

So it looks like the patch was kept in stable because i hit the problem
now after upgrading from kernel 6.9 to 6.13. It's a PCIe card which was
cheaply available in europe so it wouldn't surprise me if some more of
these are around and in use. So, can we keep supporting that chip and
revert the change, or do i have to get a new card?

Regards,

Michael


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ