From: Konstantin Shkolnyy <kshk@linux.ibm.com>
To: sgarzare@redhat.com
Cc: virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, mjrosato@linux.ibm.com,
pabeni@redhat.com, AVKrasnov@sberdevices.ru, mst@redhat.com,
Konstantin Shkolnyy <kshk@linux.ibm.com>
Subject: [PATCH net v8 0/3] vsock/test: fix wrong setsockopt() parameters
Date: Tue, 3 Dec 2024 09:06:53 -0600 [thread overview]
Message-ID: <20241203150656.287028-1-kshk@linux.ibm.com> (raw)
Parameters were created using wrong C types, which caused them to be of
wrong size on some architectures, causing problems.
The problem with SO_RCVLOWAT was found on s390 (big endian), while x86-64
didn't show it. After the fix, all tests pass on s390.
Then Stefano Garzarella pointed out that SO_VM_SOCKETS_* calls might have
a similar problem, which turned out to be true, hence, the second patch.
Changes for v8:
- Fix whitespace warnings from "checkpatch.pl --strict"
- Add maintainers to Cc:
Changes for v7:
- Rebase on top of https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
- Add the "net" tags to the subjects
Changes for v6:
- rework the patch #3 to avoid creating a new file for new functions,
and exclude vsock_perf from calling the new functions.
- add "Reviewed-by:" to the patch #2.
Changes for v5:
- in the patch #2 replace the introduced uint64_t with unsigned long long
to match documentation
- add a patch #3 that verifies every setsockopt() call.
Changes for v4:
- add "Reviewed-by:" to the first patch, and add a second patch fixing
SO_VM_SOCKETS_* calls, which depends on the first one (hence, it's now
a patch series.)
Changes for v3:
- fix the same problem in vsock_perf and update commit message
Changes for v2:
- add "Fixes:" lines to the commit message
Konstantin Shkolnyy (3):
vsock/test: fix failures due to wrong SO_RCVLOWAT parameter
vsock/test: fix parameter types in SO_VM_SOCKETS_* calls
vsock/test: verify socket options after setting them
tools/testing/vsock/control.c | 9 +-
tools/testing/vsock/msg_zerocopy_common.c | 10 --
tools/testing/vsock/msg_zerocopy_common.h | 1 -
tools/testing/vsock/util.c | 142 ++++++++++++++++++++++
tools/testing/vsock/util.h | 7 ++
tools/testing/vsock/vsock_perf.c | 20 ++-
tools/testing/vsock/vsock_test.c | 75 ++++++------
tools/testing/vsock/vsock_test_zerocopy.c | 2 +-
tools/testing/vsock/vsock_uring_test.c | 2 +-
9 files changed, 204 insertions(+), 64 deletions(-)
--
2.34.1
next reply other threads:[~2024-12-03 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 15:06 Konstantin Shkolnyy [this message]
2024-12-03 15:06 ` [PATCH net v8 1/3] vsock/test: fix failures due to wrong SO_RCVLOWAT parameter Konstantin Shkolnyy
2024-12-03 15:06 ` [PATCH net v8 2/3] vsock/test: fix parameter types in SO_VM_SOCKETS_* calls Konstantin Shkolnyy
2024-12-03 15:06 ` [PATCH net v8 3/3] vsock/test: verify socket options after setting them Konstantin Shkolnyy
2024-12-05 10:50 ` [PATCH net v8 0/3] vsock/test: fix wrong setsockopt() parameters 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=20241203150656.287028-1-kshk@linux.ibm.com \
--to=kshk@linux.ibm.com \
--cc=AVKrasnov@sberdevices.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux.dev \
/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).