From: Allison Henderson <achender@kernel.org>
To: netdev@vger.kernel.org
Cc: linux-kselftest@vger.kernel.org, pabeni@redhat.com,
edumazet@google.com, rds-devel@oss.oracle.com, kuba@kernel.org,
horms@kernel.org, linux-rdma@vger.kernel.org,
allison.henderson@oracle.com
Subject: [PATCH net-next v1 0/3] selftests: rds: ksft cleanups
Date: Sat, 7 Mar 2026 22:58:32 -0700 [thread overview]
Message-ID: <20260308055835.1338257-1-achender@kernel.org> (raw)
Hi all,
This set addresses a few rds selftests clean ups and bugs encountered
when running in the ksft framework. The first patch is a clean up
patch that addresses pylint warnings, but otherwise no functional
changes. The next patch moves the test time out to a ksft settings
file so that the time out is set appropriately. And lastly we fix a
tcpdump segfault caused by deprecated a os.fork() call.
Questions, comments and feed back appreciated!
Thanks!
Allison
Allison Henderson (3):
selftests: rds: Fix pylint warnings
selftests: rds: Add ksft timeout
selftests: rds: Fix tcpdump segfault in rds selftests
tools/testing/selftests/net/rds/Makefile | 1 +
tools/testing/selftests/net/rds/run.sh | 7 +-
tools/testing/selftests/net/rds/settings | 1 +
tools/testing/selftests/net/rds/test.py | 108 +++++++++++++----------
4 files changed, 66 insertions(+), 51 deletions(-)
create mode 100644 tools/testing/selftests/net/rds/settings
--
2.43.0
next reply other threads:[~2026-03-08 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 5:58 Allison Henderson [this message]
2026-03-08 5:58 ` [PATCH net-next v1 1/3] selftests: rds: Fix pylint warnings Allison Henderson
2026-03-08 5:58 ` [PATCH net-next v1 2/3] selftests: rds: Add ksft timeout Allison Henderson
2026-03-08 5:58 ` [PATCH net-next v1 3/3] selftests: rds: Fix tcpdump segfault in rds selftests Allison Henderson
2026-03-11 1:53 ` [PATCH net-next v1 0/3] selftests: rds: ksft cleanups Jakub Kicinski
2026-03-11 4:56 ` Allison Henderson
2026-03-12 0:05 ` Jakub Kicinski
2026-03-16 0:55 ` Jakub Kicinski
2026-03-11 2:00 ` 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=20260308055835.1338257-1-achender@kernel.org \
--to=achender@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.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