From: Jakub Kicinski <kuba@kernel.org>
To: Thomas Winter <Thomas.Winter@alliedtelesis.co.nz>
Cc: davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
pabeni@redhat.com, edumazet@google.com, a@unstable.cc,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] ip/ip6_gre: Fix changing addr gen mode not generating IPv6 link local address
Date: Tue, 24 Jan 2023 19:24:37 -0800 [thread overview]
Message-ID: <20230124192437.6d33cc06@kernel.org> (raw)
In-Reply-To: <20230124032105.79487-4-Thomas.Winter@alliedtelesis.co.nz>
On Tue, 24 Jan 2023 16:21:04 +1300 Thomas Winter wrote:
> Commit e5dd729460ca changed the code path so that GRE tunnels
> generate an IPv6 address based on the tunnel source address.
> It also changed the code path so GRE tunnels don't call addrconf_addr_gen
> in addrconf_dev_config which is called by addrconf_sysctl_addr_gen_mode
> when the IN6_ADDR_GEN_MODE is changed.
>
> This patch aims to fix this issue by moving the code in addrconf_notify
> which calls the addr gen for GRE and SIT into a separate function
> and calling it in the places that expect the IPv6 address to be
> generated.
>
> The previous addrconf_dev_config is renamed to addrconf_eth_config
> since it only expected eth type interfaces and follows the
> addrconf_gre/sit_config format.
The commit message reads like a description of the code changes,
not the problem statement + extra context it should be.
Please start with a solid description of what the problem you're seeing
is, without referring to the implementation / code at all.
You should also mention why changing the code flow for LOOPBACK is safe
as it's not visible in the patch itself. And I think the subject should
be more broad than just GRE, since you also fix SIT.
Similar comments to a smaller extent for the second patch.
When you repost please make a fresh thread.
next prev parent reply other threads:[~2023-01-25 3:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 3:21 [PATCH 0/2] ip/ip6_gre: Fix GRE tunnels not generating IPv6 link local addresses Thomas Winter
2023-01-24 3:21 ` [PATCH 1/2] ip/ip6_gre: Fix changing addr gen mode not generating IPv6 link local address Thomas Winter
2023-01-24 3:21 ` [PATCH 2/2] ip/ip6_gre: Fix non-point-to-point tunnel " Thomas Winter
2023-01-24 3:21 ` [PATCH v3 1/2] ip/ip6_gre: Fix changing addr gen mode " Thomas Winter
2023-01-25 3:24 ` Jakub Kicinski [this message]
2023-01-24 3:21 ` [PATCH v3 2/2] ip/ip6_gre: Fix non-point-to-point tunnel " Thomas Winter
2023-01-25 3:28 ` [PATCH 0/2] ip/ip6_gre: Fix GRE tunnels not generating IPv6 link local addresses Jakub Kicinski
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=20230124192437.6d33cc06@kernel.org \
--to=kuba@kernel.org \
--cc=Thomas.Winter@alliedtelesis.co.nz \
--cc=a@unstable.cc \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.