From: patchwork-bot+netdevbpf@kernel.org
To: Kibaek Yoo <psykibaek@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] net: macvlan: support multicast rx for bridge ports with shared source MAC
Date: Wed, 04 Mar 2026 02:50:06 +0000 [thread overview]
Message-ID: <177259260680.1568629.10771533628414019675.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260228071613.4360-1-psykibaek@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 28 Feb 2026 16:16:12 +0900 you wrote:
> Macvlan bridge mode currently does not handle the case where an
> external source shares its MAC address with a local macvlan interface.
> When such a frame arrives, macvlan_hash_lookup() matches the source
> MAC to the local macvlan, and macvlan_multicast_rx() assumes bridge
> ports already received the frame during local transmission. Since the
> frame actually originated externally, bridge ports never saw it.
>
> [...]
Here is the summary with links:
- [v2,1/2] net: macvlan: support multicast rx for bridge ports with shared source MAC
https://git.kernel.org/netdev/net-next/c/b52363f706e5
- [v2,2/2] selftests: net: add macvlan multicast test for shared source MAC
https://git.kernel.org/netdev/net-next/c/4ad96a7c9e2c
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-04 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 10:00 [PATCH] net: macvlan: fix multicast delivery to bridge ports with shared source MAC Kibaek Yoo
2026-02-28 3:04 ` Jakub Kicinski
2026-02-28 7:16 ` [PATCH v2 1/2] net: macvlan: support multicast rx for " Kibaek Yoo
2026-02-28 7:16 ` [PATCH v2 2/2] selftests: net: add macvlan multicast test for " Kibaek Yoo
2026-03-04 2: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=177259260680.1568629.10771533628414019675.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=psykibaek@gmail.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