From: Stefan Hajnoczi <stefanha@redhat.com>
To: Jorgen Hansen <jhansen@vmware.com>
Cc: netdev@vger.kernel.org
Subject: AF_VSOCK unimplemented sockopts
Date: Thu, 3 Aug 2017 11:41:16 +0100 [thread overview]
Message-ID: <20170803104116.GA22685@stefanha-x1.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
Hi Jorgen,
There are 3 sockopts defined in include/uapi/linux/vm_sockets.h that are
currently not implemented in net/vmw_vsock/af_vsock.c:
* SO_VM_SOCKETS_PEER_HOST_VM_ID
* SO_VM_SOCKETS_TRUSTED
* SO_VM_SOCKETS_NONBLOCK_TXRX
I noticed this because SO_VM_SOCKETS_TRUSTED is interesting for
virtio-vsock. Services listening on AF_VSOCK inside the guest may not
want arbitrary unprivileged host processes to connect. Instead of
inventing a new solution I wanted to look into SO_VM_SOCKETS_TRUSTED but
found it is not implemented in linux.git.
What is the status of these sockopts?
Thanks,
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next reply other threads:[~2017-08-03 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 10:41 Stefan Hajnoczi [this message]
2017-08-11 9:23 ` AF_VSOCK unimplemented sockopts Jorgen S. Hansen
2017-08-15 8:36 ` 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=20170803104116.GA22685@stefanha-x1.localdomain \
--to=stefanha@redhat.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