All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Zhiping Zhang <zhipingz@meta.com>
Cc: jgg@ziepe.ca, leon@kernel.org, saeedm@nvidia.com,
	tariqt@nvidia.com, mbloch@nvidia.com, michaelgur@nvidia.com,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v2] net/mlx5: free mlx5_st_idx_data on final dealloc
Date: Fri, 17 Jul 2026 10:00:08 +0000	[thread overview]
Message-ID: <178428240839.1642910.17157981121127705010.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260702222507.1234467-1-zhipingz@meta.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Thu, 2 Jul 2026 15:24:58 -0700 you wrote:
> Workloads that repeatedly allocate and release mkeys carrying TPH
> steering-tag hints (e.g. churning RDMA MRs) leak one
> struct mlx5_st_idx_data per cycle; kmemleak flags it as unreferenced
> and the kmalloc slab grows over time.
> 
> When the last reference to an ST table entry is dropped,
> mlx5_st_dealloc_index() removed the entry from idx_xa but the backing
> mlx5_st_idx_data allocation was never freed.
> 
> [...]

Here is the summary with links:
  - [net,v2] net/mlx5: free mlx5_st_idx_data on final dealloc
    https://git.kernel.org/netdev/net/c/df6134b527a8

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2026-07-17 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 22:24 [PATCH net v2] net/mlx5: free mlx5_st_idx_data on final dealloc Zhiping Zhang
2026-07-10 11:25 ` Paolo Abeni
2026-07-13  8:08   ` Leon Romanovsky
2026-07-17  9:47     ` Paolo Abeni
2026-07-17 10:00 ` patchwork-bot+netdevbpf [this message]
     [not found] <20260630165324.2859353-1-zhipingz@meta.com>
2026-07-05 14:19 ` Leon Romanovsky
2026-07-06 12:33 ` Tariq Toukan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178428240839.1642910.17157981121127705010.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=michaelgur@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=stable@vger.kernel.org \
    --cc=tariqt@nvidia.com \
    --cc=zhipingz@meta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.