From: Krasnov Arseniy Vladimirovich <AVKrasnov@sberdevices.ru>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Krasnov Arseniy <oxffffaa@gmail.com>,
Rokosov Dmitry Dmitrievich <DDRokosov@sberdevices.ru>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v4 0/2] af_vsock: add two new tests for SOCK_SEQPACKET
Date: Fri, 18 Mar 2022 05:05:26 +0000 [thread overview]
Message-ID: <bd2c956c-6cad-0873-d304-e441bfb0036f@sberdevices.ru> (raw)
In-Reply-To: <97d6d8c6-f7b2-1b03-a3d9-f312c33134ec@sberdevices.ru>
On 17.03.2022 11:29, Krasnov Arseniy Vladimirovich wrote:
Great! Thank You for reviewing this patchset!
> This adds two tests: for receive timeout and reading to invalid
> buffer provided by user. I forgot to put both patches to main
> patchset.
>
> Arseniy Krasnov(2):
>
> af_vsock: SOCK_SEQPACKET receive timeout test
> af_vsock: SOCK_SEQPACKET broken buffer test
>
> tools/testing/vsock/vsock_test.c | 215 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 215 insertions(+)
>
> v1 -> v2:
> see every patch after '---' line.
>
> v2 -> v3:
> see every patch after '---' line.
>
> v3 -> v4:
> see every patch after '---' line.
>
next prev parent reply other threads:[~2022-03-18 5:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 8:29 Krasnov Arseniy Vladimirovich
2022-03-17 8:31 ` [PATCH net-next v4 1/2] af_vsock: SOCK_SEQPACKET receive timeout test Krasnov Arseniy Vladimirovich
2022-03-17 8:49 ` Stefano Garzarella
2022-03-17 8:33 ` [PATCH net-next v4 2/2] af_vsock: SOCK_SEQPACKET broken buffer test Krasnov Arseniy Vladimirovich
2022-03-18 5:05 ` Krasnov Arseniy Vladimirovich [this message]
2022-03-18 15:30 ` [PATCH net-next v4 0/2] af_vsock: add two new tests for SOCK_SEQPACKET 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=bd2c956c-6cad-0873-d304-e441bfb0036f@sberdevices.ru \
--to=avkrasnov@sberdevices.ru \
--cc=DDRokosov@sberdevices.ru \
--cc=kvm@vger.kernel.org \
--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
all inboxes | Powered by JetHome®