From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E310438B7BD; Tue, 20 Jan 2026 23:29:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768951777; cv=none; b=XH0g2SJwU7SQmFs+jLZ5jAEwmtVZyMisHoaR24Ch+lOczGz/nGvxZzHMzsTWDKqy4ozigHxu0Noom0gDesnmJFgDhxX6Vt3rlIze5X0C/nVA0bi8pTeb+lDINDR+/bkF2J2HoGctaplJ2cDMpTGjDn/tOe9AAd7RFMGyXhDoaeA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768951777; c=relaxed/simple; bh=MnMzxsQi9s5gcx4IbSfF2YZQ7yecHRA3Ds+sFR+OjPI=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=KdtmFYsgv9zvbWprEl0Z5UYSEfFLEKCWy7btfFHMSKb3qDghmpos5loIUSYXGNw7+ZUqE9lVxb+IvU/mfyv4tOQgh65fPif5Li1VQAc+MZ8ltiNSFjUuda6Xk0Aj5e6OPPX5r0jyvpZeC+CeJ6Ffx2jdXmkrQI/q7GnT+IyqTjI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=a3zUt4kM; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="a3zUt4kM" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9EFC5C16AAE; Tue, 20 Jan 2026 23:29:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1768951776; bh=MnMzxsQi9s5gcx4IbSfF2YZQ7yecHRA3Ds+sFR+OjPI=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=a3zUt4kM7xp8pW2zQ9Y7Tym1EbX0MG2lETtqOHLfd4Tg9CwwCWtxLGhMwFcJVr3ao VK8fwsjXfNsixuflcIy1qGFCpNFMU4+fXsHkkoOAw7M9v3hXBPrV0xLcPAGdyopOPG ee0ETxm/Q8PxbY5QIdyflybfzvigXdf/Oe4nKLzLuIo5u3fhpZXqzxI6GiKRJuZ1M5 YU/LNWZNpWFQqptSjjPSGd7Wh8R4UCpJyrtWtywPovvYUmUXF+35nOwNp3js7E2TXw HutRwTJV+pR3dJIVxhWCpiWmoljkRhtKRhWbFEu1AQl8kHcYidf2noSl8XVFrrUvIY kngWB9O1zmZ0Q== Date: Tue, 20 Jan 2026 15:29:34 -0800 From: Jakub Kicinski To: Leon Hwang Cc: netdev@vger.kernel.org, Jesper Dangaard Brouer , Ilias Apalodimas , Steven Rostedt , Masami Hiramatsu , Mathieu Desnoyers , "David S . Miller" , Eric Dumazet , Paolo Abeni , Simon Horman , kerneljasonxing@gmail.com, lance.yang@linux.dev, jiayuan.chen@linux.dev, linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org, Leon Huang Fu Subject: Re: [PATCH net-next v4] page_pool: Add page_pool_release_stalled tracepoint Message-ID: <20260120152934.2eb16a11@kernel.org> In-Reply-To: References: <20260119102119.176211-1-leon.hwang@linux.dev> <20260119083759.5deeaa3c@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 =E2=80=9CClient Seek= Broker > Connection Leak=E2=80=9D [1]. The scenario you are describing matches the situations we run into=20 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=20 and doesn't have access to the already existing facilities.