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>,
Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
Sridhar Samudrala <sridhar.samudrala@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
LiLiang <liali@redhat.com>
Subject: [PATCH net-next 0/3] net: add IFF_NO_ADDRCONF to prevent ipv6 addrconf
Date: Fri, 9 Dec 2022 10:21:37 -0500 [thread overview]
Message-ID: <cover.1670599241.git.lucien.xin@gmail.com> (raw)
This patchset adds IFF_NO_ADDRCONF flag for dev->priv_flags
to prevent ipv6 addrconf, as Jiri Pirko's suggestion.
For Bonding it changes to use this flag instead of IFF_SLAVE
flag in Patch 1, and for Teaming and Net Failover it sets
this flag before calling dev_open() in Patch 2 and 3.
Xin Long (3):
net: add IFF_NO_ADDRCONF and use it in bonding to prevent ipv6
addrconf
net: team: use IFF_NO_ADDRCONF flag to prevent ipv6 addrconf
net: failover: use IFF_NO_ADDRCONF flag to prevent ipv6 addrconf
drivers/net/bonding/bond_main.c | 18 +++++++++++++-----
drivers/net/team/team.c | 2 ++
include/linux/netdevice.h | 3 ++-
net/core/failover.c | 6 +++---
net/ipv6/addrconf.c | 4 ++--
5 files changed, 22 insertions(+), 11 deletions(-)
--
2.31.1
next reply other threads:[~2022-12-09 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 15:21 Xin Long [this message]
2022-12-09 15:21 ` [PATCH net-next 1/3] net: add IFF_NO_ADDRCONF and use it in bonding to prevent ipv6 addrconf Xin Long
2022-12-09 15:21 ` [PATCH net-next 2/3] net: team: use IFF_NO_ADDRCONF flag " Xin Long
2022-12-09 15:21 ` [PATCH net-next 3/3] net: failover: " Xin Long
2022-12-12 23:30 ` [PATCH net-next 0/3] net: add IFF_NO_ADDRCONF " 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=cover.1670599241.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liali@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sridhar.samudrala@intel.com \
--cc=stephen@networkplumber.org \
--cc=vfalico@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;
as well as URLs for NNTP newsgroup(s).