From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Jiri Pirko <jiri@resnulli.us>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>
Subject: [PATCHv2 net 0/2] net: fix nsna_ping not working in team
Date: Wed, 11 Jan 2023 19:41:55 -0500 [thread overview]
Message-ID: <cover.1673483994.git.lucien.xin@gmail.com> (raw)
Completely disabling ipv6 addrconf is too harsh to team driver,
as nsna_ping link-watch still needs it. The 1st patch is to fix
it by only preventing DAD and RS sending for it, and 2nd patch
is to add a selftest for all factors that may prevent DAD and
RS sending including the team/bond slave ports.
v1->v2:
- no need to check IFF_NO_ADDRCONF addrconf_dad_begin(), see
Patch 1.
- add a selftest for DAD and RS as David Ahern suggested, see
Patch 2.
Xin Long (2):
ipv6: prevent only DAD and RS sending for IFF_NO_ADDRCONF
kselftest: add a selftest for ipv6 dad and rs sending
net/ipv6/addrconf.c | 12 +--
tools/testing/selftests/net/Makefile | 1 +
tools/testing/selftests/net/ipv6_dad_rs.sh | 111 +++++++++++++++++++++
3 files changed, 117 insertions(+), 7 deletions(-)
create mode 100755 tools/testing/selftests/net/ipv6_dad_rs.sh
--
2.31.1
next reply other threads:[~2023-01-12 0:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 0:41 Xin Long [this message]
2023-01-12 0:41 ` [PATCHv2 net 1/2] ipv6: prevent only DAD and RS sending for IFF_NO_ADDRCONF Xin Long
2023-01-14 5:33 ` Jakub Kicinski
2023-01-14 17:23 ` Xin Long
2023-01-12 0:41 ` [PATCHv2 net 2/2] kselftest: add a selftest for ipv6 dad and rs sending Xin Long
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=cover.1673483994.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@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 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).