netdev - Re: [PATCH net-next v2] net: ethernet: pcnet32: remove VLB support

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

Message-ID: <alpine.DEB.2.21.2602052244160.17548@angie.orcam.me.uk>
Date: Thu, 5 Feb 2026 23:35:14 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: OnesuchDev <enelsonmoore@...il.com>
cc: andrew+netdev@...n.ch, "David S. Miller" <davem@...emloft.net>, 
    edumazet@...gle.com, kuba@...nel.org, netdev@...r.kernel.org, 
    pabeni@...hat.com, pcnet32@...ntier.com, 
    Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Subject: Re: [PATCH net-next v2] net: ethernet: pcnet32: remove VLB support

On Wed, 4 Feb 2026, OnesuchDev wrote:

> It was not my intention to spread FUD - I had simply forgotten the 
> previous conversation when I sent this follow-up.

 I did think it was unintentional, but then someone unfamiliar with the 
situation could get misled.  Please be more careful in the future.  I tend 
to be forgetful of things too and address that by double-checking stuff.

> Do you have any issues with short stalls under high network load, like I 
> do in QEMU?

 Hard to say authoritatively.  I can't recall any issues, but then I have 
not stressed the interface recently and the load here would be different, 
as my main use for the platform is remote GNU toolchain verification for 
the MIPS target, over SSH and NFS both at a time for control and data 
respectively.  This does put a high load on the network link, especially 
as the attribute cache has to be disabled as well.

 I tend to run that over FDDI nowadays though, both to separate traffic 
and to keep the FDDI stack verified as well across platforms, of which I 
have many.  I have no GNU toolchain verification scheduled for the MIPS 
target in the near future, but can try to remember to run it over Ethernet 
instead next time.

 I would suspect QEMU though, having had used pcnet32 for 20+ years now 
and having seen all kinds of odd issues with QEMU too (and fixed some as 
well).  It's a simulator after all, and then not a very accurate one in 
terms of timings.

  Maciej