From: Petr Machata <petrm@nvidia.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Petr Machata <petrm@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
Ido Schimmel <idosch@nvidia.com>, <mlxsw@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Nikolay Aleksandrov <razor@blackwall.org>,
Roopa Prabhu <roopa@nvidia.com>,
Menglong Dong <menglong8.dong@gmail.com>,
Guillaume Nault <gnault@redhat.com>
Subject: Re: [PATCH net-next 1/4] vxlan: Join / leave MC group after remote changes
Date: Tue, 11 Feb 2025 15:56:59 +0100 [thread overview]
Message-ID: <87seoksdjh.fsf@nvidia.com> (raw)
In-Reply-To: <a800d740-0c28-4982-913b-a74e2e427f25@redhat.com>
Paolo Abeni <pabeni@redhat.com> writes:
> On 2/7/25 6:34 PM, Petr Machata wrote:
>> @@ -3899,6 +3904,11 @@ static void vxlan_config_apply(struct net_device *dev,
>> dev->mtu = conf->mtu;
>>
>> vxlan->net = src_net;
>> +
>> + } else if (vxlan->dev->flags & IFF_UP) {
>> + if (vxlan_addr_multicast(&vxlan->default_dst.remote_ip) &&
>> + rem_changed)
>> + vxlan_multicast_leave(vxlan);
>
> AFAICS vxlan_vni_update_group() is not completely ignore
> vxlan_multicast_{leave,join} errors. Instead is bailing out as soon as
> any error happens. For consistency's sake I think it would be better do
> the same here.
>
> Also I have the feeling that ending-up in an inconsistent status with no
> group joined would be less troublesome than the opposite.
This can already happen FWIW. If you currently want to change the remote
group address in a way that doesn't break things, you take the netdevice
down, then change it, then bring it back up. The leave during downing
can fail and will not be diagnosed. (Nor can it really be, you can't
veto downing.)
I can add the bail-outs that you ask for, but I don't know that there is
a way to resolve these issues for real.
next prev parent reply other threads:[~2025-02-11 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 17:34 [PATCH net-next 0/4] vxlan: Join / leave MC group when reconfigured Petr Machata
2025-02-07 17:34 ` [PATCH net-next 1/4] vxlan: Join / leave MC group after remote changes Petr Machata
2025-02-11 14:17 ` Paolo Abeni
2025-02-11 14:56 ` Petr Machata [this message]
2025-02-11 15:52 ` Paolo Abeni
2025-02-11 22:11 ` Petr Machata
2025-02-07 17:34 ` [PATCH net-next 2/4] selftests: forwarding: lib: Move require_command to net, generalize Petr Machata
2025-02-07 17:34 ` [PATCH net-next 3/4] selftests: test_vxlan_fdb_changelink: Convert to lib.sh Petr Machata
2025-02-07 17:34 ` [PATCH net-next 4/4] selftests: test_vxlan_fdb_changelink: Add a test for MC remote change Petr Machata
2025-02-10 11:24 ` [PATCH net-next 0/4] vxlan: Join / leave MC group when reconfigured Nikolay Aleksandrov
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=87seoksdjh.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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;
as well as URLs for NNTP newsgroup(s).