From: Hangbin Liu <hangbin.liu@linux.dev>
To: Xuanqiang Luo <xuanqiang.luo@linux.dev>
Cc: netdev@vger.kernel.org, idosch@nvidia.com, dsahern@kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, tgraf@suug.ch,
pshelar@nicira.com, linux-kernel@vger.kernel.org,
luoxuanqiang@kylinos.cn
Subject: Re: [PATCH net v2] ip_gre: Reject enabling collect metadata through changelink
Date: Wed, 23 Sep 2026 09:05:45 +0800 [thread overview]
Message-ID: <arMl6ePySuNonC4I@fedora> (raw)
In-Reply-To: <20260921031859.9283-1-xuanqiang.luo@linux.dev>
On Mon, Sep 21, 2026 at 11:18:59AM +0800, Xuanqiang Luo wrote:
> From: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
>
> ipgre_netlink_parms() can enable collect_md on an existing GRE, GRETAP
> or ERSPAN device. Unlike newlink, changelink does not enforce metadata
> tunnel uniqueness. Converting a non-metadata device can therefore
> replace the metadata receive entry for another device of the same type
> in the same netns. Deleting either device then clears the shared entry,
> breaking metadata receive lookup for the surviving device.
>
> If parameter validation fails after collect_md is set, deleting the
> modified device can also clear an entry it never owned.
>
> Reject enabling metadata mode in both changelink callbacks before any
> encapsulation or tunnel parameters are modified. Allow requests that
> repeat the metadata attribute on an existing metadata device.
>
> Fixes: 2e15ea390e6f ("ip_gre: Add support to collect tunnel metadata.")
> Signed-off-by: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
> ---
> Changes:
> v2:
> - Add an extack message when rejecting collect_md enablement in both
> changelink callbacks. (Ido Schimmel.)
> - Rebase onto the latest net/main.
>
> v1: https://lore.kernel.org/all/20260917095016.71937-1-xuanqiang.luo@linux.dev/
>
> The state change on failure can be reproduced without an existing
> metadata tunnel (output abbreviated):
>
> # ip link add g1 type gre local 192.0.2.1 remote 192.0.2.2
> # ip -d link show g1
> link/gre 192.0.2.1 peer 192.0.2.2 ...
> gre remote 192.0.2.2 local 192.0.2.1 ...
>
> # ip link set g1 type gre external
> RTNETLINK answers: Invalid argument
>
> # ip -d link show g1
> link/none c0:00:02:01 peer c0:00:02:02 ...
> gre external remote 192.0.2.2 local 192.0.2.1 ...
>
> # ip link del g1
>
> The request fails, but collect_md and the device type have already
> changed.
>
> If another metadata tunnel exists, deleting this device can clear its
> collect_md_tun entry. A successful conversion can overwrite that entry.
>
> net/ipv4/ip_gre.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/net/ipv4/ip_gre.c b/net/ipv4/ip_gre.c
> index 82309efd417e0..e4878e9aa6367 100644
> --- a/net/ipv4/ip_gre.c
> +++ b/net/ipv4/ip_gre.c
> @@ -1464,6 +1464,12 @@ static int ipgre_changelink(struct net_device *dev, struct nlattr *tb[],
> if (!rtnl_dev_link_net_capable(dev, t->net))
> return -EPERM;
>
> + if (data && data[IFLA_GRE_COLLECT_METADATA] && !t->collect_md) {
> + NL_SET_ERR_MSG(extack,
> + "Enabling collect_md on an existing device is not supported");
> + return -EOPNOTSUPP;
> + }
> +
> err = ipgre_newlink_encap_setup(dev, data);
> if (err)
> return err;
> @@ -1496,6 +1502,12 @@ static int erspan_changelink(struct net_device *dev, struct nlattr *tb[],
> if (!rtnl_dev_link_net_capable(dev, t->net))
> return -EPERM;
>
> + if (data && data[IFLA_GRE_COLLECT_METADATA] && !t->collect_md) {
> + NL_SET_ERR_MSG(extack,
> + "Enabling collect_md on an existing device is not supported");
> + return -EOPNOTSUPP;
> + }
> +
> err = ipgre_newlink_encap_setup(dev, data);
> if (err)
> return err;
>
> base-commit: 1e24c4f2ee44be0eee94092b5d13cbdb4bdf0d60
> --
> 2.43.0
>
Reviewed-by: Hangbin Liu <liuhangbin@kylinos.cn>
next prev parent reply other threads:[~2026-09-23 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 3:18 [PATCH net v2] ip_gre: Reject enabling collect metadata through changelink Xuanqiang Luo
2026-09-21 11:32 ` Ido Schimmel
2026-09-23 1:05 ` Hangbin Liu [this message]
2026-09-24 2:30 ` 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=arMl6ePySuNonC4I@fedora \
--to=hangbin.liu@linux.dev \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luoxuanqiang@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@nicira.com \
--cc=tgraf@suug.ch \
--cc=xuanqiang.luo@linux.dev \
/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.