From: patchwork-bot+netdevbpf@kernel.org
To: Minhong He <heminhong@kylinos.cn>
Cc: horms@kernel.org, andrea.mayer@uniroma2.it, davem@davemloft.net,
david.lebrun@uclouvain.be, dsahern@kernel.org,
edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net v3] ipv6: add NULL checks for idev in SRv6 paths
Date: Thu, 19 Mar 2026 00:44:17 +0000 [thread overview]
Message-ID: <177388105728.935482.13380611320476992951.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260316073301.106643-1-heminhong@kylinos.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 Mar 2026 15:33:01 +0800 you wrote:
> __in6_dev_get() can return NULL when the device has no IPv6 configuration
> (e.g. MTU < IPV6_MIN_MTU or after NETDEV_UNREGISTER).
>
> Add NULL checks for idev returned by __in6_dev_get() in both
> seg6_hmac_validate_skb() and ipv6_srh_rcv() to prevent potential NULL
> pointer dereferences.
>
> [...]
Here is the summary with links:
- [net,v3] ipv6: add NULL checks for idev in SRv6 paths
https://git.kernel.org/netdev/net/c/064137935262
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-03-19 0:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 7:23 [PATCH net] ipv6: sr: Add unlikely hint to idev NULL check in seg6_hmac_validate_skb Minhong He
2026-03-11 8:57 ` Eric Dumazet
2026-03-13 2:26 ` [PATCH net v2] ipv6: sr: Add NULL check for idev " Minhong He
2026-03-13 2:38 ` Jakub Kicinski
2026-03-14 22:49 ` Andrea Mayer
2026-03-15 16:01 ` [net,v2] " Simon Horman
2026-03-16 7:33 ` [PATCH net v3] ipv6: add NULL checks for idev in SRv6 paths Minhong He
2026-03-18 0:51 ` Andrea Mayer
2026-03-19 0:44 ` 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=177388105728.935482.13380611320476992951.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrea.mayer@uniroma2.it \
--cc=davem@davemloft.net \
--cc=david.lebrun@uclouvain.be \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=heminhong@kylinos.cn \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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