All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Myeonghun Pak <mhun512@gmail.com>
Cc: rmody@marvell.com, skalluru@marvell.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, GR-Linux-NIC-Dev@marvell.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, ae878000@gmail.com
Subject: Re: [PATCH net] bna: prevent IOC timer rearm during teardown
Date: Thu, 24 Sep 2026 11:10:05 +0000	[thread overview]
Message-ID: <179024820515.1482887.3609644266293399580.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260922014605.588040-1-mhun512@gmail.com>

Hello:

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

On Mon, 21 Sep 2026 21:46:05 -0400 you wrote:
> bna: prevent IOC timer rearm during teardown
> 
> bnad_pci_remove() and the probe disable_ioceth path call
> timer_delete_sync() for ioc_timer, sem_timer and hb_timer, but not for
> iocpf_timer.  bnad_iocpf_timeout() then takes bnad->bna_lock after
> free_netdev() has freed the struct bnad.
> 
> [...]

Here is the summary with links:
  - [net] bna: prevent IOC timer rearm during teardown
    https://git.kernel.org/netdev/net/c/77b1718e39e5

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



      reply	other threads:[~2026-09-24 11:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  1:46 [PATCH net] bna: prevent IOC timer rearm during teardown Myeonghun Pak
2026-09-24 11:10 ` 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=179024820515.1482887.3609644266293399580.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=GR-Linux-NIC-Dev@marvell.com \
    --cc=ae878000@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhun512@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rmody@marvell.com \
    --cc=skalluru@marvell.com \
    --cc=stable@vger.kernel.org \
    /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.