From: Chuck Lever <chuck.lever@oracle.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 00/10] mount.nfs support for netids
Date: Tue, 08 Dec 2009 12:59:09 -0500 [thread overview]
Message-ID: <20091208175128.2544.457.stgit@localhost.localdomain> (raw)
Hi Steve-
For 2.6.33, Trond has included Jeff's patch that adds support to the
kernel NFS client for "proto=netid." Here are the user space changes
we think are necessary to complete this support. See:
https://bugzilla.redhat.com/show_bug.cgi?id=479350
This series has seen some light testing here, and Jeff is planning to
do more of his own independent testing.
Note that last patch in the series has a rather full set of updates
to nfs(5) that document NFS client side support for NFS over IPv6,
including support for "proto=netid."
Please have a look and let me know what you think.
---
Chuck Lever (10):
NFS man page: update nfs(5) with details about IPv6 support
mount.nfs: Remove nfs_name_to_address()
mount.nfs: Teach umount.nfs to recognize netids in /etc/mtab
mount.nfs: proto=netid forces address family when resolving server names
mount.nfs: Fix sockaddr pointer aliasing in stropts.c
mount.nfs: Add new API for getting protocol family from netids
mount.nfs: make nfs_lookup() global
mount.nfs: support netids in v2/v3 version/transport negotiation
mount.nfs: support netids in nfs_options2pmap()
libnfs.a: Provide shared helpers for managing netids
support/include/nfsrpc.h | 12 ++++
support/nfs/getport.c | 92 +++++++++++++++++++++++++++++++--
utils/mount/network.c | 128 ++++++++++++++++++++++++++++++----------------
utils/mount/network.h | 5 +-
utils/mount/nfs.man | 104 ++++++++++++++++++++++++++-----------
utils/mount/nfsumount.c | 15 ++++-
utils/mount/stropts.c | 114 +++++++++++++++++++++++------------------
7 files changed, 331 insertions(+), 139 deletions(-)
--
Chuck Lever <chuck.lever@oracle.com>
next reply other threads:[~2009-12-08 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 17:59 Chuck Lever [this message]
[not found] ` <20091208175128.2544.457.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-12-08 17:59 ` [PATCH 01/10] libnfs.a: Provide shared helpers for managing netids Chuck Lever
2009-12-08 17:59 ` [PATCH 02/10] mount.nfs: support netids in nfs_options2pmap() Chuck Lever
2009-12-08 17:59 ` [PATCH 03/10] mount.nfs: support netids in v2/v3 version/transport negotiation Chuck Lever
2009-12-08 17:59 ` [PATCH 04/10] mount.nfs: make nfs_lookup() global Chuck Lever
2009-12-08 18:00 ` [PATCH 05/10] mount.nfs: Add new API for getting protocol family from netids Chuck Lever
2009-12-08 18:00 ` [PATCH 06/10] mount.nfs: Fix sockaddr pointer aliasing in stropts.c Chuck Lever
2009-12-08 18:00 ` [PATCH 07/10] mount.nfs: proto=netid forces address family when resolving server names Chuck Lever
2009-12-08 18:00 ` [PATCH 08/10] mount.nfs: Teach umount.nfs to recognize netids in /etc/mtab Chuck Lever
2009-12-08 18:00 ` [PATCH 09/10] mount.nfs: Remove nfs_name_to_address() Chuck Lever
2009-12-08 18:00 ` [PATCH 10/10] NFS man page: update nfs(5) with details about IPv6 support Chuck Lever
2009-12-11 21:17 ` [PATCH 00/10] mount.nfs support for netids 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=20091208175128.2544.457.stgit@localhost.localdomain \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@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