Thread (7 messages) 7 messages, 3 authors, 2026-01-21

Re: [PATCH net-next v4] page_pool: Add page_pool_release_stalled tracepoint

From: Jakub Kicinski <kuba@kernel.org>
Date: 2026-01-20 23:29:36
Also in: lkml, netdev

On Tue, 20 Jan 2026 11:16:20 +0800 Leon Hwang wrote:
I encountered the 'pr_warn()' messages during Mellanox NIC flapping on a
system using the 'mlx5_core' driver (kernel 6.6). The root cause turned
out to be an application-level issue: the IBM/sarama “Client SeekBroker
Connection Leak” [1].
The scenario you are describing matches the situations we run into 
at Meta. With the upstream kernel you can find that the pages are
leaking based on stats, and if you care use drgn to locate them
(in the recv queue).

The 6.6 kernel did not have page pool stats. I feel quite odd about
adding more uAPI because someone is running a 2+ years old kernel 
and doesn't have access to the already existing facilities.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help