search for: vsock_test

...l data is gone and EOF is returned, so we should skip the read > of data written by the peer before closing the connection. > > Reported-by: Jorgen Hansen <jhansen at vmware.com> > Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> > --- > tools/testing/vsock/vsock_test.c | 26 ++++++++++++++++++++++++-- > 1 file changed, 24 insertions(+), 2 deletions(-) > > diff --git a/tools/testing/vsock/vsock_test.c b/tools/testing/vsock/vsock_test.c > index cb606091489f..64adf45501ca 100644 > --- a/tools/testing/vsock/vsock_test.c > +++ b/tools/testing/vsoc...

From: Stefan Hajnoczi <stefanha at redhat.com> The vsock_test.c program runs a test suite of AF_VSOCK test cases. Signed-off-by: Stefan Hajnoczi <stefanha at redhat.com> Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> --- v2: * Drop unnecessary includes [Stefan] * Aligned with the current SPDX [Stefano] * Set MULTICONN_NFDS to 100 [...

...ality has no tests. This patch series adds several test cases that exercise AF_VSOCK SOCK_STREAM socket semantics (send/recv, connect/accept, half-closed connections, simultaneous connections). Stefan: Do you think we should have a single application or is better to split it in single tests (e.g. vsock_test_send_recv, vsock_test_half_close, vsock_test_multiconnection, etc.)? Jorgen: Please test the VMCI transport and let me know if the fixes work. I added the '--transport' parameter to skip the read() on the half-closed connection test. Dexuan: Do you think can be useful to test HyperV? The...

...guest closes a connection, all data is gone and EOF is returned, so we should skip the read of data written by the peer before closing the connection. Reported-by: Jorgen Hansen <jhansen at vmware.com> Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> --- tools/testing/vsock/vsock_test.c | 26 ++++++++++++++++++++++++-- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/tools/testing/vsock/vsock_test.c b/tools/testing/vsock/vsock_test.c index cb606091489f..64adf45501ca 100644 --- a/tools/testing/vsock/vsock_test.c +++ b/tools/testing/vsock/vsock_test.c @@ -71,6 +71,7...

...test into single applications, one for each test, do you think it makes sense? Or is it just a useless complication? Thanks, Stefano On Thu, Aug 1, 2019 at 5:27 PM Stefano Garzarella <sgarzare at redhat.com> wrote: > > From: Stefan Hajnoczi <stefanha at redhat.com> > > The vsock_test.c program runs a test suite of AF_VSOCK test cases. > > Signed-off-by: Stefan Hajnoczi <stefanha at redhat.com> > Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> > --- > v2: > * Drop unnecessary includes [Stefan] > * Aligned with the current SPDX [Stefa...

...test into single applications, one for each test, do you think it makes sense? Or is it just a useless complication? Thanks, Stefano On Thu, Aug 1, 2019 at 5:27 PM Stefano Garzarella <sgarzare at redhat.com> wrote: > > From: Stefan Hajnoczi <stefanha at redhat.com> > > The vsock_test.c program runs a test suite of AF_VSOCK test cases. > > Signed-off-by: Stefan Hajnoczi <stefanha at redhat.com> > Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> > --- > v2: > * Drop unnecessary includes [Stefan] > * Aligned with the current SPDX [Stefa...

...iers to vsock tests VSOCK: extract utility functions from vsock_diag_test.c VSOCK: extract connect/accept functions from vsock_diag_test.c VSOCK: add full barrier between test cases VSOCK: add send_byte()/recv_byte() test utilities VSOCK: add AF_VSOCK test cases Stefano Garzarella (4): vsock_test: wait for the remote to close the connection testing/vsock: add parameters to list and skip tests testing/vsock: print list of options and description vsock_test: add SOCK_STREAM MSG_PEEK test tools/testing/vsock/.gitignore | 1 + tools/testing/vsock/Makefile | 9 +- too...

On Thu, Aug 01, 2019 at 04:16:37PM +0000, Dexuan Cui wrote: > > From: Stefano Garzarella <sgarzare at redhat.com> > > Sent: Thursday, August 1, 2019 8:26 AM > > > > The vsock_diag.ko module already has a test suite but the core AF_VSOCK > > functionality has no tests. This patch series adds several test cases that > > exercise AF_VSOCK SOCK_STREAM socket

...rote: >This adds two tests for 'shutdown()' call. It checks that SIGPIPE is >sent when MSG_NOSIGNAL is not set and vice versa. Both flags SHUT_WR >and SHUT_RD are tested. > >Signed-off-by: Arseniy Krasnov <avkrasnov at salutedevices.com> >--- > tools/testing/vsock/vsock_test.c | 138 +++++++++++++++++++++++++++++++ > 1 file changed, 138 insertions(+) Reviewed-by: Stefano Garzarella <sgarzare at redhat.com> > >diff --git a/tools/testing/vsock/vsock_test.c b/tools/testing/vsock/vsock_test.c >index 90718c2fd4ea..148fc9c47c50 100644 >--- a/tools/testi...

...>This adds test which checks case when data of newly received skbuff is >appended to the last skbuff in the socket's queue. > >This test is actual only for virtio transport. > >Signed-off-by: Arseniy Krasnov <AVKrasnov at sberdevices.ru> >--- > tools/testing/vsock/vsock_test.c | 81 ++++++++++++++++++++++++++++++++ > 1 file changed, 81 insertions(+) > >diff --git a/tools/testing/vsock/vsock_test.c b/tools/testing/vsock/vsock_test.c >index 3de10dbb50f5..00216c52d8b6 100644 >--- a/tools/testing/vsock/vsock_test.c >+++ b/tools/testing/vsock/vsock_test.c &...

...ACKET call 'skb_pull()' also in case of copy failure or >>> ? dropping skbuff (when we just waiting message end). >>> - Handle copy failure for SOCK_STREAM in the same manner (plus free >>> ? current skbuff). >>> - Replace bug repdroducer with new test in vsock_test.c >>> >>> v2 -> v3: >>> - Replace patch which removes 'skb->len' subtraction from function >>> ? 'virtio_transport_dec_rx_pkt()' with patch which updates functions >>> ? 'virtio_transport_inc/dec_rx_pkt()' by passing integer...

...at.com> > --- > drivers/vhost/vsock.c | 30 ++++++++++++++++++------------ > 1 file changed, 18 insertions(+), 12 deletions(-) The changes for vsock part LGTM: Reviewed-by: Stefano Garzarella <sgarzare at redhat.com> I also did some tests with vhost-vsock (tools/testing/vsock/vsock_test and iperf-vsock), so for vsock: Tested-by: Stefano Garzarella <sgarzare at redhat.com> Thanks, Stefano > > diff --git a/drivers/vhost/vsock.c b/drivers/vhost/vsock.c > index a483cec31d5c..61c6d3dd2ae3 100644 > --- a/drivers/vhost/vsock.c > +++ b/drivers/vhost/vsock.c > @...

...at.com> > --- > drivers/vhost/vsock.c | 30 ++++++++++++++++++------------ > 1 file changed, 18 insertions(+), 12 deletions(-) The changes for vsock part LGTM: Reviewed-by: Stefano Garzarella <sgarzare at redhat.com> I also did some tests with vhost-vsock (tools/testing/vsock/vsock_test and iperf-vsock), so for vsock: Tested-by: Stefano Garzarella <sgarzare at redhat.com> Thanks, Stefano > > diff --git a/drivers/vhost/vsock.c b/drivers/vhost/vsock.c > index a483cec31d5c..61c6d3dd2ae3 100644 > --- a/drivers/vhost/vsock.c > +++ b/drivers/vhost/vsock.c > @...

...vsock.c | 30 ++++++++++++++++++------------ > > 1 file changed, 18 insertions(+), 12 deletions(-) > > The changes for vsock part LGTM: > > Reviewed-by: Stefano Garzarella <sgarzare at redhat.com> > > > I also did some tests with vhost-vsock (tools/testing/vsock/vsock_test > and iperf-vsock), so for vsock: > > Tested-by: Stefano Garzarella <sgarzare at redhat.com> > > Thanks, > Stefano Re-testing v6 would be very much appreciated. > > > > diff --git a/drivers/vhost/vsock.c b/drivers/vhost/vsock.c > > index a483cec31d5c.....

This adds infrastructure required for supporting multiple ring formats. The idea is as follows: we convert descriptors to an independent format first, and process that converting to iov later. Used ring is similar: we fetch into an independent struct first, convert that to IOV later. The point is that we have a tight loop that fetches descriptors, which is good for cache utilization. This will