On Wed, Sep 13, 2017 at 12:21 PM,= Christoph Hellwig <hch@infradead.org> wrote:
Please get your VSOCK NFS transport into the ietf NFSv4= working group
first before moving forward with Linux support - we should not implement non-standardized extensions.

On Wed, Sep 13, 2017 at 11:26:36AM +0100, Stefan Hajnoczi wrote:
> * The last revision was somewhat controversial because it's alre= ady possible
> to share files between a hypervisor and virtual machine u= sing TCP/IP, so why
> add AF_VSOCK support to the stack? TCP/IP based sol= utions require the
> virtual machine administrator to be involved in the confi= guration and are
> therefore not suitable for automatic management by OpenSt= ack, oVirt, etc.
> Maintainers, is this feature acceptable?
>
> * Need advice on netid: is there agreement to use "tcpv&quo= t; instead of "vsock" as
> Chuck Lever suggested and how to ask IESG to assign it? >
> The AF_VSOCK address family allows virtual machines to communicate wit= h the
> hypervisor using a zero-configuration transport. KVM, VMware, an= d Hyper-V
> hypervisors support AF_VSOCK and it was first introduced in Linux 3.9.=
>
> This patch series adds AF_VSOCK support to mount.nfs(8) and rpc.nfsd(8= ). To
> mount an export from the hypervisor (CID 2):
>
> # mount.nfs 2:/srv/vm01 /mnt -o proto=3Dvsock
>
> To serve exports over vsock port 2049:
>
> # nfsd ... --vsock 2049
>
> This series extends exports(5) syntax to handle vsock:<CID> or v= sock:*. For
> example, the guest with CID 3 can be given access using vsock:3.
>
> nfsd can export over IPv4/IPv6 and vsock at the same time. See t= he changes to
> exports.man, nfs.man, and nfsd.man in the patches for syntax details.<= br> >
> NFSv4 and later are supported.
>
> The code is also available here:
> https://github.com/stefanha/nfs-util= s/tree/vsock-nfsd
>
> The latest kernel patches are available here:
> https://github.com/stefanha/linux/tree/vs= ock-nfsd
>
> Stefan Hajnoczi (14):
> mount: don't use IPPROTO_UDP for address resolution
> nfs-utils: add vsock.h
> nfs-utils: add AF_VSOCK support to sockaddr.h
> mount: present AF_VSOCK addresses
> mount: accept AF_VSOCK in nfs_verify_family()
> mount: generate AF_VSOCK clientaddr
> getport: recognize "vsock" netid
> mount: AF_VSOCK address parsing
> exportfs: introduce host_freeaddrinfo()
> exportfs: add AF_VSOCK address parsing and printing
> exportfs: add AF_VSOCK support to set_addrlist()
> exportfs: add support for "vsock:" exports(5) sy= ntax
> nfsd: add --vsock (-v) option to nfsd
> tests: add "vsock:" exports(5) test case
>
> tests/Makefile.am | &nbs= p;3 +-
> support/include/exportfs.h | 4 ++
> support/include/sockaddr.h | 18 +++++<= br> > support/include/vsock.h | 59 +++&= #43;+++++++++++++
> utils/nfsd/nfssvc.h | 1 &= #43;
> support/export/client.c | 8 +--
> support/export/hostname.c | 161 +++++&= #43;++++++++++++++&= #43;+++++++++++++&= #43;++++++++--
> support/nfs/getport.c | 16 ++&= #43;--
> utils/exportfs/exportfs.c | 42 ++++&= #43;+++++--
> utils/mount/network.c | 37 ++&= #43;+++++++-
> utils/mount/stropts.c | 61 ++&= #43;+++++++++++---
> utils/mountd/auth.c | 2 &= #43;-
> utils/mountd/cache.c | 10 +-= -
> utils/mountd/mountd.c | 4 +-=
> utils/mountd/rmtab.c | 2 &= #43;-
> utils/nfsd/nfsd.c | 18 &= #43;+++-
> utils/nfsd/nfssvc.c | 62 +&= #43;++++++++++++++&= #43;
> configure.ac = ;| 3 +
> tests/t0002-vsock-basic.sh | 53 +++++&= #43;+++++++++
> utils/exportfs/exports.man | 12 +++-
> utils/mount/nfs.man | 20 +&= #43;++--
> utils/nfsd/nfsd.man | 4 &= #43;+
> 22 files changed, 552 insertions(+), 48 deletions(-)
> create mode 100644 support/include/vsock.h
> create mode 100755 tests/t0002-vsock-basic.sh
>
> --
> 2.13.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-n= fs" in
> the body of a message to = majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/<= wbr>majordomo-info.html
---end quoted text---

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4