From: Stefan Hajnoczi <stefanha@redhat.com>
To: Jorgen Hansen <jhansen@vmware.com>
Cc: Dexuan Cui <decui@microsoft.com>, netdev@vger.kernel.org
Subject: AF_VSOCK connection refused errno
Date: Tue, 12 Dec 2017 15:53:52 +0000 [thread overview]
Message-ID: <20171212155352.GA10090@stefanha-x1.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
When connect(2) fails because the peer is not listening the virtio vsock
transport returns ECONNRESET. I believe the VMCI transport does the
same (based on code inspection).
Jorgen: Can you confirm this VMCI transport behavior?
I'd like to change to ECONNREFUSED for all transports because developers
will be surprised when they get ECONNRESET. It makes porting AF_INET
code harder.
On the other hand, it may be too late to fix this if there userspace
applications that rely on ECONNRESET? I'm not aware of any such
applications myself.
Thanks,
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next reply other threads:[~2017-12-12 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 15:53 Stefan Hajnoczi [this message]
2017-12-13 10:28 ` AF_VSOCK connection refused errno Jorgen S. Hansen
2017-12-13 14:58 ` Stefan Hajnoczi
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=20171212155352.GA10090@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=decui@microsoft.com \
--cc=jhansen@vmware.com \
--cc=netdev@vger.kernel.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