From: Nikolay Aleksandrov <razor@blackwall.org>
To: Hangbin Liu <liuhangbin@gmail.com>, netdev@vger.kernel.org
Cc: Jay Vosburgh <jv@jvosburgh.net>,
Andy Gospodarek <andy@greyhouse.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv4 net 1/2] bonding: add ns target multicast address to slave device
Date: Tue, 12 Nov 2024 15:54:40 +0200 [thread overview]
Message-ID: <8ef7f9ea-dd5e-48fd-a20c-13bc6b1e1505@blackwall.org> (raw)
In-Reply-To: <20241111101650.27685-2-liuhangbin@gmail.com>
On 11/11/24 12:16, Hangbin Liu wrote:
> Commit 4598380f9c54 ("bonding: fix ns validation on backup slaves")
> tried to resolve the issue where backup slaves couldn't be brought up when
> receiving IPv6 Neighbor Solicitation (NS) messages. However, this fix only
> worked for drivers that receive all multicast messages, such as the veth
> interface.
>
> For standard drivers, the NS multicast message is silently dropped because
> the slave device is not a member of the NS target multicast group.
>
> To address this, we need to make the slave device join the NS target
> multicast group, ensuring it can receive these IPv6 NS messages to validate
> the slave’s status properly.
>
> There are three policies before joining the multicast group:
> 1. All settings must be under active-backup mode (alb and tlb do not support
> arp_validate), with backup slaves and slaves supporting multicast.
> 2. We can add or remove multicast groups when arp_validate changes.
> 3. Other operations, such as enslaving, releasing, or setting NS targets,
> need to be guarded by arp_validate.
>
> Fixes: 4e24be018eb9 ("bonding: add new parameter ns_targets")
> Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
> ---
> drivers/net/bonding/bond_main.c | 16 +++++-
> drivers/net/bonding/bond_options.c | 82 +++++++++++++++++++++++++++++-
> include/net/bond_options.h | 2 +
> 3 files changed, 98 insertions(+), 2 deletions(-)
>
Looks good to me,
Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
next prev parent reply other threads:[~2024-11-12 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 10:16 [PATCHv4 net 0/2] bonding: fix ns targets not work on hardware NIC Hangbin Liu
2024-11-11 10:16 ` [PATCHv4 net 1/2] bonding: add ns target multicast address to slave device Hangbin Liu
2024-11-12 13:54 ` Nikolay Aleksandrov [this message]
2024-11-11 10:16 ` [PATCHv4 net 2/2] selftests: bonding: add ns multicast group testing Hangbin Liu
2024-11-12 13:55 ` Nikolay Aleksandrov
2024-11-14 10:20 ` [PATCHv4 net 0/2] bonding: fix ns targets not work on hardware NIC patchwork-bot+netdevbpf
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=8ef7f9ea-dd5e-48fd-a20c-13bc6b1e1505@blackwall.org \
--to=razor@blackwall.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--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
all inboxes | Powered by JetHome®