From: Hangbin Liu <liuhangbin@gmail.com>
To: netdev@vger.kernel.org
Cc: Jay Vosburgh <j.vosburgh@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Toppins <jtoppins@redhat.com>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>, liali <liali@redhat.com>,
Saeed Mahameed <saeed@kernel.org>,
Hangbin Liu <liuhangbin@gmail.com>
Subject: [PATCH net 0/3] Bonding: fix high prio not effect issue
Date: Mon, 12 Dec 2022 11:56:44 +0800 [thread overview]
Message-ID: <20221212035647.1053865-1-liuhangbin@gmail.com> (raw)
When a high prio link up, if there has current link, it will not do
failover as we missed the check in link up event. Fix it in this patchset
and add a prio option test case.
v2:
1. use rcu_access_pointer() instead of rtnl_dereference().
2: make do_failover after looping all slaves
Hangbin Liu (2):
bonding: add missed __rcu annotation for curr_active_slave
bonding: do failover when high prio link up
Liang Li (1):
selftests: bonding: add bonding prio option test
drivers/net/bonding/bond_main.c | 24 +-
.../selftests/drivers/net/bonding/Makefile | 3 +-
.../drivers/net/bonding/option_prio.sh | 245 ++++++++++++++++++
3 files changed, 262 insertions(+), 10 deletions(-)
create mode 100755 tools/testing/selftests/drivers/net/bonding/option_prio.sh
--
2.38.1
next reply other threads:[~2022-12-12 3:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 3:56 Hangbin Liu [this message]
2022-12-12 3:56 ` [PATCHv2 net 1/3] bonding: add missed __rcu annotation for curr_active_slave Hangbin Liu
2022-12-12 3:56 ` [PATCHv2 net 2/3] bonding: do failover when high prio link up Hangbin Liu
2022-12-12 3:56 ` [PATCHv2 net 3/3] selftests: bonding: add bonding prio option test Hangbin Liu
2022-12-14 3:30 ` [PATCH net 0/3] Bonding: fix high prio not effect issue patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2022-12-09 10:13 Hangbin Liu
2022-12-10 0:01 ` Jay Vosburgh
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=20221212035647.1053865-1-liuhangbin@gmail.com \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=jtoppins@redhat.com \
--cc=kuba@kernel.org \
--cc=liali@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.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).