From: Steve Dickson <SteveD@RedHat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Felix Janda <felix.janda@posteo.de>,
linux-nfs@vger.kernel.org, Jeff Layton <jlayton@redhat.com>,
Abbas Naderi <abiusx@google.com>
Subject: Re: [PATCH nfs-utils v2 03/12] mount: present AF_VSOCK addresses
Date: Wed, 12 Jul 2017 10:26:02 -0400 [thread overview]
Message-ID: <4e57a6f2-87a2-b601-4727-041f6bffcdff@RedHat.com> (raw)
In-Reply-To: <20170710181447.GW14195@stefanha-x1.localdomain>
On 07/10/2017 02:14 PM, Stefan Hajnoczi wrote:
> On Mon, Jul 03, 2017 at 12:51:07PM -0400, Steve Dickson wrote:
>> On 07/03/2017 05:00 AM, Stefan Hajnoczi wrote:
>>> On Fri, Jun 30, 2017 at 10:40:49AM -0400, Steve Dickson wrote:
>>>> On 06/30/2017 09:21 AM, Stefan Hajnoczi wrote:
>> Are there other implementations out there that would cause breakage?
>> I'm pretty sure nfs-utils is only used in Linux environments, right?
>
> Does nfs-utils have a set of minimum distro versions that are supported?
Not that I'm aware of... Now there are certain package versions nfs-utils
is dependent on but not particular distro.
steved.
>
> For example, "the latest nfs-utils release is supported on RHEL 6, SLES
> 11, and Debian 8 jessie".
>
> If yes, then I could go check that these distros ship AF_VSOCK and
> <linux/vm_sockets.h>.
>
> Stefan
>
next prev parent reply other threads:[~2017-07-12 14:26 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 13:21 [PATCH nfs-utils v2 00/12] add NFS over AF_VSOCK support Stefan Hajnoczi
2017-06-30 13:21 ` [PATCH nfs-utils v2 01/12] mount: don't use IPPROTO_UDP for address resolution Stefan Hajnoczi
2017-06-30 14:34 ` Steve Dickson
2017-07-03 8:55 ` Stefan Hajnoczi
2017-07-03 16:35 ` Steve Dickson
2017-06-30 13:21 ` [PATCH nfs-utils v2 02/12] nfs-utils: add AF_VSOCK support to sockaddr.h Stefan Hajnoczi
2017-06-30 13:21 ` [PATCH nfs-utils v2 03/12] mount: present AF_VSOCK addresses Stefan Hajnoczi
2017-06-30 14:40 ` Steve Dickson
2017-07-03 9:00 ` Stefan Hajnoczi
2017-07-03 16:51 ` Steve Dickson
2017-07-03 21:04 ` Felix Janda
2017-07-10 18:14 ` Stefan Hajnoczi
2017-07-12 14:26 ` Steve Dickson [this message]
2017-07-06 17:16 ` J. Bruce Fields
2017-07-10 18:09 ` Stefan Hajnoczi
2017-06-30 13:21 ` [PATCH nfs-utils v2 04/12] mount: accept AF_VSOCK in nfs_verify_family() Stefan Hajnoczi
2017-06-30 13:21 ` [PATCH nfs-utils v2 05/12] getport: recognize "vsock" netid Stefan Hajnoczi
2017-06-30 15:01 ` Steve Dickson
2017-07-10 18:35 ` Stefan Hajnoczi
2017-06-30 15:52 ` Chuck Lever
2017-07-07 3:17 ` NeilBrown
2017-07-07 4:13 ` NeilBrown
2017-07-25 10:05 ` Stefan Hajnoczi
2017-07-27 5:13 ` NeilBrown
2017-07-27 10:58 ` Stefan Hajnoczi
2017-07-27 11:33 ` Jeff Layton
2017-07-27 23:11 ` NeilBrown
2017-08-03 15:24 ` Stefan Hajnoczi
2017-08-03 21:45 ` NeilBrown
2017-08-03 23:53 ` Matt Benjamin
2017-08-04 3:25 ` NeilBrown
2017-08-04 15:56 ` Stefan Hajnoczi
2017-08-04 22:35 ` NeilBrown
2017-08-08 14:07 ` Stefan Hajnoczi
2017-07-07 4:14 ` Chuck Lever
2017-07-25 12:29 ` Stefan Hajnoczi
2017-07-19 15:11 ` Stefan Hajnoczi
2017-07-19 15:35 ` Jeff Layton
2017-07-19 15:40 ` Chuck Lever
2017-07-19 15:50 ` Chuck Lever
2017-07-28 0:35 ` Matt Benjamin
2017-06-30 13:21 ` [PATCH nfs-utils v2 06/12] mount: AF_VSOCK address parsing Stefan Hajnoczi
2017-06-30 13:21 ` [PATCH nfs-utils v2 07/12] exportfs: introduce host_freeaddrinfo() Stefan Hajnoczi
2017-06-30 13:21 ` [PATCH nfs-utils v2 08/12] exportfs: add AF_VSOCK address parsing and printing Stefan Hajnoczi
2017-06-30 13:21 ` [PATCH nfs-utils v2 09/12] exportfs: add AF_VSOCK support to set_addrlist() Stefan Hajnoczi
2017-06-30 13:21 ` [PATCH nfs-utils v2 10/12] exportfs: add support for "vsock:" exports(5) syntax Stefan Hajnoczi
2017-06-30 15:07 ` Steve Dickson
2017-06-30 13:21 ` [PATCH nfs-utils v2 11/12] nfsd: add --vsock (-v) option to nfsd Stefan Hajnoczi
2017-06-30 15:25 ` Steve Dickson
2017-07-10 18:39 ` Stefan Hajnoczi
2017-06-30 13:21 ` [PATCH nfs-utils v2 12/12] tests: add "vsock:" exports(5) test case 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=4e57a6f2-87a2-b601-4727-041f6bffcdff@RedHat.com \
--to=steved@redhat.com \
--cc=abiusx@google.com \
--cc=felix.janda@posteo.de \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=stefanha@redhat.com \
/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