From: patchwork-bot+netdevbpf@kernel.org
To: Jun Yang <juny24602@gmail.com>
Cc: netdev@vger.kernel.org, junvyyang@tencent.com, stable@kernel.org,
corvus@tencent.com, jmaloy@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, ying.xue@windriver.com,
tipc-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] tipc: read le->link under the node lock in tipc_node_link_down()
Date: Tue, 11 Aug 2026 14:00:31 +0000 [thread overview]
Message-ID: <178645683164.537263.7714780493708130841.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260810102147.48191-1-juny24602@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 10 Aug 2026 18:21:38 +0800 you wrote:
> From: Jun Yang <junvyyang@tencent.com>
>
> tipc_node_link_down() caches the link pointer before taking n->lock:
>
> struct tipc_link *l = le->link; /* unlocked */
>
> if (!l)
> return;
> tipc_node_write_lock(n);
> if (!tipc_link_is_establishing(l)) { /* deref l */
> ...
> tipc_link_reset(l); /* write into l */
> if (delete) {
> kfree(l);
> le->link = NULL;
>
> [...]
Here is the summary with links:
- [net,v2] tipc: read le->link under the node lock in tipc_node_link_down()
https://git.kernel.org/netdev/net/c/cba9ccb47e9f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-11 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 10:21 [PATCH net v2] tipc: read le->link under the node lock in tipc_node_link_down() Jun Yang
2026-08-10 11:01 ` Tung Quang Nguyen
2026-08-11 12:01 ` Tung Quang Nguyen
2026-08-11 14:00 ` 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=178645683164.537263.7714780493708130841.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corvus@tencent.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jmaloy@redhat.com \
--cc=junvyyang@tencent.com \
--cc=juny24602@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox