From: Jakub Kicinski <kuba@kernel.org>
To: Stanislav Fomichev <stfomichev@gmail.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Jiri Pirko <jiri@resnulli.us>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Network Development <netdev@vger.kernel.org>,
Ido Schimmel <idosch@nvidia.com>, Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH net v2] team: avoid NETDEV_CHANGEMTU event when unregistering slave
Date: Thu, 29 Jan 2026 19:12:43 -0800 [thread overview]
Message-ID: <20260129191243.767e3005@kernel.org> (raw)
In-Reply-To: <aXl_MwhS9AJXTYi4@mini-arch>
On Tue, 27 Jan 2026 19:14:59 -0800 Stanislav Fomichev wrote:
> > problem. Ido Schimmel found steps to reproduce
> >
> > ip link add name team1 type team
> > ip link add name dummy1 mtu 1499 master team1 type dummy
> > ip netns add ns1
> > ip link set dev dummy1 netns ns1
> > ip -n ns1 link del dev dummy1
>
> Can we add the above as a selftest to
> tools/testing/selftests/net/rtnetlink.sh? I was adding the quirky ones
> (like kci_test_macsec_vlan) over there.. Or maybe something under
> selftests/drivers/net/team/ ?
Under selftests/drivers/net/team/ please, rtnetlink.sh is too much
of a catch-all.
--
pw-bot: cr
next prev parent reply other threads:[~2026-01-30 3:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 11:05 [PATCH net v2] team: avoid NETDEV_CHANGEMTU event when unregistering slave Tetsuo Handa
2026-01-28 3:14 ` Stanislav Fomichev
2026-01-30 3:12 ` Jakub Kicinski [this message]
2026-02-22 7:16 ` Tetsuo Handa
2026-02-22 9:34 ` Ido Schimmel
2026-02-22 11:19 ` [PATCH] selftests/net: team: add team unregister test Tetsuo Handa
2026-02-22 13:17 ` [PATCH v2] " Tetsuo Handa
2026-02-22 15:32 ` Ido Schimmel
2026-02-22 15:40 ` Tetsuo Handa
2026-02-22 17:39 ` Ido Schimmel
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=20260129191243.767e3005@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=stfomichev@gmail.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