From: patchwork-bot+netdevbpf@kernel.org
To: Konstantin Shkolnyy <kshk@linux.ibm.com>
Cc: sgarzare@redhat.com, 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
Subject: Re: [PATCH net v8 0/3] vsock/test: fix wrong setsockopt() parameters
Date: Thu, 05 Dec 2024 10:50:31 +0000 [thread overview]
Message-ID: <173339583150.1545533.78880242047414570.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241203150656.287028-1-kshk@linux.ibm.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 3 Dec 2024 09:06:53 -0600 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [net,v8,1/3] vsock/test: fix failures due to wrong SO_RCVLOWAT parameter
https://git.kernel.org/netdev/net/c/7ce1c0921a80
- [net,v8,2/3] vsock/test: fix parameter types in SO_VM_SOCKETS_* calls
https://git.kernel.org/netdev/net/c/3f36ee29e732
- [net,v8,3/3] vsock/test: verify socket options after setting them
https://git.kernel.org/netdev/net/c/86814d8ffd55
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-12-05 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 15:06 [PATCH net v8 0/3] vsock/test: fix wrong setsockopt() parameters Konstantin Shkolnyy
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 ` patchwork-bot+netdevbpf [this message]
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=173339583150.1545533.78880242047414570.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=AVKrasnov@sberdevices.ru \
--cc=kshk@linux.ibm.com \
--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).