From: Jonathan Toppins <jtoppins@redhat.com>
To: netdev@vger.kernel.org
Cc: liuhangbin@gmail.com
Subject: [PATCH net v3 0/2] bonding: 802.3ad: fix no transmission of LACPDUs
Date: Mon, 15 Aug 2022 11:08:33 -0400 [thread overview]
Message-ID: <cover.1660572700.git.jtoppins@redhat.com> (raw)
The first patch adds some kselftest infrastructure and the reproducer
that demonstrates the problem. The second patch fixes the issue.
v3:
* rebased to latest net/master
* addressed comment from Hangbin
Jonathan Toppins (2):
selftests: include bonding tests into the kselftest infra
bonding: 802.3ad: fix no transmission of LACPDUs
MAINTAINERS | 1 +
drivers/net/bonding/bond_3ad.c | 3 +-
tools/testing/selftests/Makefile | 1 +
.../selftests/drivers/net/bonding/Makefile | 6 ++
.../net/bonding/bond-break-lacpdu-tx.sh | 81 +++++++++++++++++++
.../selftests/drivers/net/bonding/config | 1 +
.../selftests/drivers/net/bonding/settings | 1 +
7 files changed, 93 insertions(+), 1 deletion(-)
create mode 100644 tools/testing/selftests/drivers/net/bonding/Makefile
create mode 100755 tools/testing/selftests/drivers/net/bonding/bond-break-lacpdu-tx.sh
create mode 100644 tools/testing/selftests/drivers/net/bonding/config
create mode 100644 tools/testing/selftests/drivers/net/bonding/settings
--
2.31.1
next reply other threads:[~2022-08-15 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 15:08 Jonathan Toppins [this message]
2022-08-15 15:08 ` [PATCH net v3 1/2] selftests: include bonding tests into the kselftest infra Jonathan Toppins
2022-08-16 7:28 ` Hangbin Liu
2022-08-15 15:08 ` [PATCH net v3 2/2] bonding: 802.3ad: fix no transmission of LACPDUs Jonathan Toppins
2022-08-16 7:29 ` Hangbin Liu
2022-08-16 13:11 ` Jay Vosburgh
2022-08-16 13:41 ` Jonathan Toppins
2022-08-16 17:47 ` Jonathan Toppins
2022-08-17 23:24 ` 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=cover.1660572700.git.jtoppins@redhat.com \
--to=jtoppins@redhat.com \
--cc=liuhangbin@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).