All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Chengfeng Ye <nicoyip.dev@gmail.com>
Cc: tung.quang.nguyen@est.tech, jmaloy@redhat.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	tipc-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v3] tipc: protect node reset trace dump with node lock
Date: Fri, 28 Aug 2026 21:40:11 +0000	[thread overview]
Message-ID: <178795321139.2809934.6718042248113223796.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260825190141.242219-1-nicoyip.dev@gmail.com>

Hello:

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

On Wed, 26 Aug 2026 03:01:41 +0800 you wrote:
> The tipc_node_reset_links trace event asks tipc_node_dump() to walk the
> node's link entries. Unlike the other node events that request link data,
> this event runs without the node lock.
> 
> This permits bearer teardown to free a link while the trace callback is
> dumping it:
> 
> [...]

Here is the summary with links:
  - [net,v3] tipc: protect node reset trace dump with node lock
    https://git.kernel.org/netdev/net/c/dddf197f29ba

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-08-28 21:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 12:29 [PATCH net v2] tipc: protect node reset trace dump with node lock Chengfeng Ye
2026-08-25 11:08 ` Tung Quang Nguyen
2026-08-25 19:02   ` Chengfeng Ye
2026-08-25 19:01 ` [PATCH net v3] " Chengfeng Ye
2026-08-28  2:22   ` Tung Quang Nguyen
2026-08-28 21:40   ` 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=178795321139.2809934.6718042248113223796.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicoyip.dev@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=tung.quang.nguyen@est.tech \
    /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.