From: Guillaume Nault <gnault@redhat.com>
To: Gary Guo <gary@garyguo.net>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>, Aiden Yang <ling@moedove.com>
Subject: Re: [PATCH net 1/2] gre: Fix IPv6 multicast route creation.
Date: Fri, 11 Jul 2025 19:07:25 +0200 [thread overview]
Message-ID: <aHFEzWcTCy4vnlBB@debian> (raw)
In-Reply-To: <20250710135757.60581077@eugeo>
On Thu, Jul 10, 2025 at 01:57:57PM +0100, Gary Guo wrote:
> On Wed, 9 Jul 2025 16:30:10 +0200
> Guillaume Nault <gnault@redhat.com> wrote:
>
> > Use addrconf_add_dev() instead of ipv6_find_idev() in
> > addrconf_gre_config() so that we don't just get the inet6_dev, but also
> > install the default ff00::/8 multicast route.
> >
> > Before commit 3e6a0243ff00 ("gre: Fix again IPv6 link-local address
> > generation."), the multicast route was created at the end of the
> > function by addrconf_add_mroute(). But this code path is now only taken
> > in one particular case (gre devices not bound to a local IP address and
> > in EUI64 mode). For all other cases, the function exits early and
> > addrconf_add_mroute() is not called anymore.
> >
> > Using addrconf_add_dev() instead of ipv6_find_idev() in
> > addrconf_gre_config(), fixes the problem as it will create the default
> > multicast route for all gre devices. This also brings
> > addrconf_gre_config() a bit closer to the normal netdevice IPv6
> > configuration code (addrconf_dev_config()).
> >
> > Fixes: 3e6a0243ff00 ("gre: Fix again IPv6 link-local address generation.")
> > Reported-by: Aiden Yang <ling@moedove.com>
> > Closes: https://lore.kernel.org/netdev/CANR=AhRM7YHHXVxJ4DmrTNMeuEOY87K2mLmo9KMed1JMr20p6g@mail.gmail.com/
> > Reviewed-by: Gary Guo <gary@garyguo.net>
> > Tested-by: Gary Guo <gary@garyguo.net>
> > Signed-off-by: Guillaume Nault <gnault@redhat.com>
>
> You probably also want to
>
> Cc: stable@vger.kernel.org
>
> so this gets picked up by the stable team after it's merged.
Yeah, I forgot that the policy had changed.
It seems that Jakub took care of it anyway.
Thanks again!
> Best,
> Gary
>
next prev parent reply other threads:[~2025-07-11 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 14:30 [PATCH net 0/2] gre: Fix default IPv6 multicast route creation Guillaume Nault
2025-07-09 14:30 ` [PATCH net 1/2] gre: Fix " Guillaume Nault
2025-07-10 11:32 ` Ido Schimmel
2025-07-10 12:57 ` Gary Guo
2025-07-11 17:07 ` Guillaume Nault [this message]
2025-07-09 14:30 ` [PATCH net 2/2] selftests: Add IPv6 multicast route generation tests for GRE devices Guillaume Nault
2025-07-10 11:33 ` Ido Schimmel
2025-07-11 16:56 ` Guillaume Nault
2025-07-11 1:30 ` [PATCH net 0/2] gre: Fix default IPv6 multicast route creation 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=aHFEzWcTCy4vnlBB@debian \
--to=gnault@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gary@garyguo.net \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=ling@moedove.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;
as well as URLs for NNTP newsgroup(s).