netdev - Re: [PATCH net-next 0/3] net: ethtool: Track TX pause storm

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: <20260123120512.162ae4d9@kernel.org>
Date: Fri, 23 Jan 2026 12:05:12 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Florian Fainelli <florian.fainelli@...adcom.com>
Cc: Mohsin Bashir <mohsin.bashr@...il.com>, netdev@...r.kernel.org,
 alexanderduyck@...com, alok.a.tiwari@...cle.com, andrew+netdev@...n.ch,
 andrew@...n.ch, chuck.lever@...cle.com, davem@...emloft.net,
 donald.hunter@...il.com, edumazet@...gle.com, gal@...dia.com,
 horms@...nel.org, idosch@...dia.com, jacob.e.keller@...el.com,
 kernel-team@...a.com, kory.maincent@...tlin.com, lee@...ger.us,
 o.rempel@...gutronix.de, pabeni@...hat.com, vadim.fedorenko@...ux.dev
Subject: Re: [PATCH net-next 0/3] net: ethtool: Track TX pause storm

On Fri, 23 Jan 2026 11:36:33 -0800 Florian Fainelli wrote:
> On 1/22/26 11:21, Mohsin Bashir wrote:
> > With TX pause enabled, if a device cannot deliver received frames to
> > the stack (e.g., during a system hang), it may generate excessive pause
> > frames causing a pause storm. This series updates the uAPI to track TX
> > pause storm events as part of the pause stats (p1), adds pause storm
> > protection support for fbnic (p2), and leverages p1 to provide
> > observability into these events for fbnic (p3).  
> 
> Jakub, should I go ahead and re-submit this patch series then:
> 
> https://patchew.org/linux/20251107002510.1678369-1-florian.fainelli@broadcom.com/

Sounded like Oleksij is also interested so let's go ahead.
Presumably an attr in ethtool -a/-A ?

> Looks like this is exactly what you ran into here.

Kinda, the machines reboot on panic. The problematic cases are those
that crashed in a way that didn't trigger normal reboot cycle. 
Or got wedge somewhere funny.