From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
avkrasnov@salutedevices.com,
virtualization@lists.linux-foundation.org, oxffffaa@gmail.com,
bobby.eshleman@bytedance.com
Subject: Re: [PATCH net-next 0/5] vsock/test: add recv_buf()/send_buf() utility functions and some improvements
Date: Sun, 17 Sep 2023 16:50:24 +0000 [thread overview]
Message-ID: <169496942446.18728.7629668615433862698.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230915121452.87192-1-sgarzare@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 15 Sep 2023 14:14:47 +0200 you wrote:
> We recently found that some tests were failing [1].
>
> The problem was that we were not waiting for all the bytes correctly,
> so we had a partial read. I had initially suggested using MSG_WAITALL,
> but this could have timeout problems.
>
> Since we already had send_byte() and recv_byte() that handled the timeout,
> but also the expected return value, I moved that code to two new functions
> that we can now use to send/receive generic buffers.
>
> [...]
Here is the summary with links:
- [net-next,1/5] vsock/test: add recv_buf() utility function
(no matching commit)
- [net-next,2/5] vsock/test: use recv_buf() in vsock_test.c
https://git.kernel.org/netdev/net-next/c/a0bcb8357716
- [net-next,3/5] vsock/test: add send_buf() utility function
(no matching commit)
- [net-next,4/5] vsock/test: use send_buf() in vsock_test.c
https://git.kernel.org/netdev/net-next/c/2a8548a9bb4c
- [net-next,5/5] vsock/test: track bytes in MSG_PEEK test for SOCK_SEQPACKET
https://git.kernel.org/netdev/net-next/c/bc7bea452d32
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:[~2023-09-17 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 12:14 [PATCH net-next 0/5] vsock/test: add recv_buf()/send_buf() utility functions and some improvements Stefano Garzarella
2023-09-15 12:14 ` [PATCH net-next 1/5] vsock/test: add recv_buf() utility function Stefano Garzarella
2023-09-15 19:23 ` Arseniy Krasnov
2023-09-15 12:14 ` [PATCH net-next 2/5] vsock/test: use recv_buf() in vsock_test.c Stefano Garzarella
2023-09-15 19:24 ` Arseniy Krasnov
2023-09-15 12:14 ` [PATCH net-next 3/5] vsock/test: add send_buf() utility function Stefano Garzarella
2023-09-15 19:25 ` Arseniy Krasnov
2023-09-15 12:14 ` [PATCH net-next 4/5] vsock/test: use send_buf() in vsock_test.c Stefano Garzarella
2023-09-15 19:26 ` Arseniy Krasnov
2023-09-15 12:14 ` [PATCH net-next 5/5] vsock/test: track bytes in MSG_PEEK test for SOCK_SEQPACKET Stefano Garzarella
2023-09-15 19:29 ` Arseniy Krasnov
2023-09-15 19:30 ` [PATCH net-next 0/5] vsock/test: add recv_buf()/send_buf() utility functions and some improvements Arseniy Krasnov
2023-09-17 16: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=169496942446.18728.7629668615433862698.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=avkrasnov@salutedevices.com \
--cc=bobby.eshleman@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux-foundation.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