From: patchwork-bot+netdevbpf@kernel.org
To: Wenbo Sun <sunwenbo@cmss.chinamobile.com>
Cc: ap420073@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
1342116488@qq.com
Subject: Re: [PATCH net] amt: use ipv6_hdr() in amt_mldv1_leave_handler()
Date: Thu, 12 Nov 2026 18:50:08 +0000 [thread overview]
Message-ID: <179450940877.590019.1220237437365570850.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261111031147.105834-1-sunwenbo@cmss.chinamobile.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 11 Nov 2026 11:11:47 +0800 you wrote:
> In amt_mldv1_leave_handler(), which handles IPv6 MLDv1 Done
> (ICMPV6_MGM_REDUCTION) messages, the source address is mistakenly
> extracted via ip_hdr(skb)->saddr into host.ip4 instead of copying the
> IPv6 source address from ipv6_hdr(skb)->saddr into host.ip6 as
> amt_mldv1_report_handler() does.
>
> Because amt_lookup_group() compares the full union amt_addr for v6
> groups, looking up the group with a 32-bit IPv4 header slice fails to
> match the group entry created by amt_mldv1_report_handler(). As a
> result, amt_del_group() is not called when an MLDv1 listener leaves,
> and the AMT relay continues forwarding multicast traffic until the
> group timer expires.
>
> [...]
Here is the summary with links:
- [net] amt: use ipv6_hdr() in amt_mldv1_leave_handler()
https://git.kernel.org/netdev/net/c/6730fe495c35
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-11-12 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 3:11 Wenbo Sun
2026-11-12 18:50 ` 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=179450940877.590019.1220237437365570850.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=1342116488@qq.com \
--cc=andrew+netdev@lunn.ch \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sunwenbo@cmss.chinamobile.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
all inboxes | Powered by JetHome®