From: Chuck Lever <chuck.lever@oracle.com>
To: jlayton@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [RFC] [PATCH 0/4] Protocol family negotiation in mount.nfs
Date: Fri, 22 Jan 2010 16:06:12 -0500 [thread overview]
Message-ID: <20100122210221.10598.84522.stgit@localhost.localdomain> (raw)
Hi Jeff-
For the record, here are patches that add support to mount.nfs for
negotiating the protocol family correctly with servers that have both
IPv4 and IPv6 addresses.
I've done some basic testing here against Solaris NFS servers, Linux
with rpcbind (Fedora 12), and Linux with portmap (Ubuntu 9.10).
---
Chuck Lever (4):
text-based mount: Support protocol family negotiation
text-based mount: Set addr= option in nfs_try_mount_foo()
text-based mount: Replace nfs_lookup() with getaddrinfo(3)
text-based mount: Retry when server can't be reached
utils/mount/nfs.man | 6 ++
utils/mount/stropts.c | 120 ++++++++++++++++++++++++++++++++++++++++++-------
2 files changed, 107 insertions(+), 19 deletions(-)
--
chuck[dot]lever[at]oracle[dot]com
next reply other threads:[~2010-01-22 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 21:06 Chuck Lever [this message]
[not found] ` <20100122210221.10598.84522.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-22 21:06 ` [PATCH 1/4] text-based mount: Retry when server can't be reached Chuck Lever
[not found] ` <20100122210621.10598.15244.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-02-05 14:31 ` Jeff Layton
2010-01-22 21:06 ` [PATCH 2/4] text-based mount: Replace nfs_lookup() with getaddrinfo(3) Chuck Lever
2010-01-22 21:06 ` [PATCH 3/4] text-based mount: Set addr= option in nfs_try_mount_foo() Chuck Lever
2010-01-22 21:06 ` [PATCH 4/4] text-based mount: Support protocol family negotiation Chuck Lever
2010-02-12 18:46 ` [RFC] [PATCH 0/4] Protocol family negotiation in mount.nfs Steve Dickson
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=20100122210221.10598.84522.stgit@localhost.localdomain \
--to=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@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