From: Arseniy Krasnov <avkrasnov@sberdevices.ru>
To: Stefan Hajnoczi <stefanha@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Bobby Eshleman <bobby.eshleman@bytedance.com>
Cc: <kvm@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@sberdevices.ru>, <oxffffaa@gmail.com>,
<avkrasnov@sberdevices.ru>
Subject: [RFC PATCH v1 0/2] return errors other than -ENOMEM to socket
Date: Sun, 26 Mar 2023 01:12:09 +0300 [thread overview]
Message-ID: <97f19214-ba04-c47e-7486-72e8aa16c690@sberdevices.ru> (raw)
Hello,
this patchset removes behaviour, where error code returned from any
transport was always switched to ENOMEM. This works in the same way as
patch from Bobby Eshleman:
commit c43170b7e157 ("vsock: return errors other than -ENOMEM to socket"),
but for receive calls.
vsock_test suite is also updated.
Arseniy Krasnov (2):
vsock: return errors other than -ENOMEM to socket
vsock/test: update expected return values
net/vmw_vsock/af_vsock.c | 4 ++--
tools/testing/vsock/vsock_test.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.25.1
next reply other threads:[~2023-03-25 22:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 22:12 Arseniy Krasnov [this message]
2023-03-25 22:13 ` [RFC PATCH v1 1/2] vsock: " Arseniy Krasnov
2023-03-28 9:39 ` Stefano Garzarella
2023-03-28 9:42 ` Stefano Garzarella
2023-03-28 10:42 ` Arseniy Krasnov
2023-03-28 11:19 ` Stefano Garzarella
2023-03-28 11:20 ` Arseniy Krasnov
2023-03-29 21:44 ` Vishnu Dasa
2023-03-30 5:13 ` Arseniy Krasnov
2023-03-25 22:14 ` [RFC PATCH v1 2/2] vsock/test: update expected return values Arseniy Krasnov
2023-03-28 9:44 ` Stefano Garzarella
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=97f19214-ba04-c47e-7486-72e8aa16c690@sberdevices.ru \
--to=avkrasnov@sberdevices.ru \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@sberdevices.ru \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@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®