From: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
To: Stefano Garzarella <sgarzare@redhat.com>,
"edumazet@google.com" <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: Bobby Eshleman <bobby.eshleman@bytedance.com>,
Krasnov Arseniy <oxffffaa@gmail.com>,
Arseniy Krasnov <AVKrasnov@sberdevices.ru>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
kernel <kernel@sberdevices.ru>
Subject: [RFC PATCH v3 1/4] vsock: return errors other than -ENOMEM to socket
Date: Sun, 4 Dec 2022 19:19:20 +0000 [thread overview]
Message-ID: <b9ea0ff4-3aef-030e-0a9b-e2fcb67b305b@sberdevices.ru> (raw)
In-Reply-To: <6bd77692-8388-8693-f15f-833df1fa6afd@sberdevices.ru>
From: Bobby Eshleman <bobby.eshleman@bytedance.com>
This removes behaviour, where error code returned from any
transport was always switched to ENOMEM.
Signed-off-by: Bobby Eshleman <bobby.eshleman@bytedance.com>
Signed-off-by: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
---
net/vmw_vsock/af_vsock.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
index 884eca7f6743..61ddab664c33 100644
--- a/net/vmw_vsock/af_vsock.c
+++ b/net/vmw_vsock/af_vsock.c
@@ -1862,8 +1862,9 @@ static int vsock_connectible_sendmsg(struct socket *sock, struct msghdr *msg,
written = transport->stream_enqueue(vsk,
msg, len - total_written);
}
+
if (written < 0) {
- err = -ENOMEM;
+ err = written;
goto out_err;
}
--
2.25.1
next prev parent reply other threads:[~2022-12-04 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 19:17 [RFC PATCH v3 0/4] vsock: update tools and error handling Arseniy Krasnov
2022-12-04 19:19 ` Arseniy Krasnov [this message]
2022-12-05 13:16 ` [RFC PATCH v3 1/4] vsock: return errors other than -ENOMEM to socket Stefano Garzarella
2022-12-04 19:20 ` [RFC PATCH v3 2/4] test/vsock: rework message bounds test Arseniy Krasnov
2022-12-05 13:24 ` Stefano Garzarella
2022-12-04 19:22 ` [RFC PATCH v3 3/4] test/vsock: add big message test Arseniy Krasnov
2022-12-04 19:24 ` [RFC PATCH v3 4/4] test/vsock: vsock_perf utility Arseniy Krasnov
2022-12-05 14:00 ` Stefano Garzarella
2022-12-06 5:25 ` Arseniy Krasnov
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=b9ea0ff4-3aef-030e-0a9b-e2fcb67b305b@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=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=pabeni@redhat.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®