All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hongyan Xu <getshell@seu.edu.cn>
Cc: sgoutham@marvell.com, rkannoth@marvell.com, gakula@marvell.com,
	sbhatta@marvell.com, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	jianhao.xu@seu.edu.cn
Subject: Re: [PATCH net] net: octeontx2-af: quiesce devlink health work on teardown
Date: Fri, 02 Oct 2026 00:50:06 +0000	[thread overview]
Message-ID: <179090220617.3161824.3912138082480407859.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928134129.145-1-getshell@seu.edu.cn>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 28 Sep 2026 21:41:29 +0800 you wrote:
> NPA and NIX interrupt handlers queue health-reporting work whose
> containers are freed by rvu_health_reporters_destroy(). Interrupt
> unregistration does not drain queued work. In addition, each reporter
> setup creates a workqueue in the same field, leaking the NPA queue and
> leaving no teardown handle for work queued on it.
> 
> Initialize work before later allocations can fail, share one workqueue,
> unregister each set of interrupts, and cancel its work before freeing
> the reporters. Destroy the shared workqueue once both reporter sets are
> gone.
> 
> [...]

Here is the summary with links:
  - [net] net: octeontx2-af: quiesce devlink health work on teardown
    https://git.kernel.org/netdev/net-next/c/1b7bc043cd1b

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-10-02  0:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 13:41 [PATCH net] net: octeontx2-af: quiesce devlink health work on teardown Hongyan Xu
2026-09-28 13:46 ` netdev-bot+sinfo
2026-10-02  0:50 ` patchwork-bot+netdevbpf [this message]

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=179090220617.3161824.3912138082480407859.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=gakula@marvell.com \
    --cc=getshell@seu.edu.cn \
    --cc=jianhao.xu@seu.edu.cn \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.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.