From: patchwork-bot+netdevbpf@kernel.org
To: Quan Sun <2022090917019@std.uestc.edu.cn>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
fmaurer@redhat.com, bigeasy@linutronix.de, luka.gejak@linux.dev,
mingo@kernel.org, arvid.brodin@alten.se
Subject: Re: [PATCH net] net: hsr: fix NULL pointer dereference in hsr_get_node_data()
Date: Tue, 12 May 2026 10:40:06 +0000 [thread overview]
Message-ID: <177858240630.2796465.7028277115824206441.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260508124636.1462346-1-2022090917019@std.uestc.edu.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 8 May 2026 20:46:36 +0800 you wrote:
> In the HSR (High-availability Seamless Redundancy) protocol, node
> information is maintained in the node_db. When a supervision frame is
> received, node->addr_B_port is updated to track the receiving port type
> (e.g., HSR_PT_SLAVE_B).
>
> If the underlying physical interface associated with this slave port is
> removed (e.g., via `ip link del`), hsr_del_port() frees the hsr_port
> object. However, the stale node->addr_B_port reference is kept in the
> node_db until the node ages out.
>
> [...]
Here is the summary with links:
- [net] net: hsr: fix NULL pointer dereference in hsr_get_node_data()
https://git.kernel.org/netdev/net/c/911f54771ca9
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-05-12 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 12:46 [PATCH net] net: hsr: fix NULL pointer dereference in hsr_get_node_data() Quan Sun
2026-05-12 10: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=177858240630.2796465.7028277115824206441.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=2022090917019@std.uestc.edu.cn \
--cc=arvid.brodin@alten.se \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fmaurer@redhat.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=luka.gejak@linux.dev \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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