From: Jonathan Toppins <jtoppins@redhat.com>
To: netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>
Subject: [PATCH net-next 0/2] bonding: fix bond recovery in mode 2
Date: Fri, 18 Nov 2022 15:30:11 -0500 [thread overview]
Message-ID: <cover.1668800711.git.jtoppins@redhat.com> (raw)
When a bond is configured with a non-zero updelay and in mode 2 the bond
never recovers after all slaves lose link. The first patch adds
selftests that demonstrate the issue and the second patch fixes the
issue by ignoring the updelay when there are no usable slaves.
Jonathan Toppins (2):
selftests: bonding: up/down delay w/ slave link flapping
bonding: fix link recovery in mode 2 when updelay is nonzero
drivers/net/bonding/bond_main.c | 11 +-
.../selftests/drivers/net/bonding/Makefile | 4 +-
.../selftests/drivers/net/bonding/lag_lib.sh | 107 ++++++++++++++++++
.../net/bonding/mode-1-recovery-updelay.sh | 45 ++++++++
.../net/bonding/mode-2-recovery-updelay.sh | 45 ++++++++
.../selftests/drivers/net/bonding/settings | 2 +-
6 files changed, 211 insertions(+), 3 deletions(-)
create mode 100755 tools/testing/selftests/drivers/net/bonding/mode-1-recovery-updelay.sh
create mode 100755 tools/testing/selftests/drivers/net/bonding/mode-2-recovery-updelay.sh
--
2.31.1
next reply other threads:[~2022-11-18 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 20:30 Jonathan Toppins [this message]
2022-11-18 20:30 ` [PATCH net-next 1/2] selftests: bonding: up/down delay w/ slave link flapping Jonathan Toppins
2022-11-22 10:53 ` Paolo Abeni
2022-11-18 20:30 ` [PATCH net-next 2/2] bonding: fix link recovery in mode 2 when updelay is nonzero Jonathan Toppins
2022-11-22 10:59 ` Paolo Abeni
2022-11-22 13:36 ` Jonathan Toppins
2022-11-22 14:45 ` Paolo Abeni
2022-11-22 15:37 ` Jonathan Toppins
2022-11-22 21:12 ` Nikolay Aleksandrov
2022-11-22 21:15 ` Nikolay Aleksandrov
2022-11-22 21:17 ` Jonathan Toppins
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.1668800711.git.jtoppins@redhat.com \
--to=jtoppins@redhat.com \
--cc=j.vosburgh@gmail.com \
--cc=netdev@vger.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).