From: Jeff Layton <jlayton@redhat.com>
To: linux-nfs@vger.kernel.org
Cc: chuck.lever@oracle.com, steved@redhat.com
Subject: [PATCH 0/6] nfs-utils: add IPv6 support for rpc.nfsd (try #2)
Date: Tue, 26 May 2009 11:15:45 -0400 [thread overview]
Message-ID: <1243350951-13462-1-git-send-email-jlayton@redhat.com> (raw)
This is the second attempt to add support IPv6 to rpc.nfsd. The main
changes since the last patchset are:
1) the addition of a patch that makes nfsd look at /etc/netconfig when
tirpc is enabled, and to disable any family/protocol combinations that
don't have visible netid's.
2) stop linking in some unneeded .a libs.
3) some minor bugfixes
4) update to the nfsd manpage for new options
I think the set is bisectable, but have only really tested the final
result. I've also tested the final result when built with tirpc enabled
and disabled, and ipv6 enabled and disabled.
I haven't seen any regressions when testing on recent mainline kernels
and The only real difference that anyone may notice is that when IPv6
support is built in, and the kernel doesn't support IPv6, nfsd logs this
message a couple of times when starting nfsd:
nfssvc: writing fds to kernel failed: errno 97 (Address family not supported by protocol)
Most of the testing I've done has been by watching the program under
strace. Since most of the kernel work for IPv6 support hasn't made it
to mainline, it's a little difficult to do much testing of this beyond
that.
Jeff Layton (6):
nfs-utils: don't link libexport.a and libmisc.a to nfsd
nfs-utils: break up nfssvc.c into more individually callable
functions
nfs-utils: set IPV6_V6ONLY on nfssvc IPv6 sockets
nfs-utils: add IPv6 support to nfsd
nfs-utils: limit protocols and families used by nfsd to those listed
in /etc/netconfig
nfs-utils: add -4 and -6 options to nfsd manpage
support/include/nfslib.h | 8 ++-
support/nfs/nfssvc.c | 164 +++++++++++++++++++++++++++++++++----------
utils/nfsd/Makefile.am | 4 +-
utils/nfsd/nfsd.c | 175 ++++++++++++++++++++++++++++++++++++++--------
utils/nfsd/nfsd.man | 10 +++
5 files changed, 292 insertions(+), 69 deletions(-)
next reply other threads:[~2009-05-26 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 15:15 Jeff Layton [this message]
2009-05-26 15:15 ` [PATCH 1/6] nfs-utils: don't link libexport.a and libmisc.a to nfsd Jeff Layton
2009-05-26 15:15 ` [PATCH 2/6] nfs-utils: break up nfssvc.c into more individually callable functions Jeff Layton
2009-05-26 15:15 ` [PATCH 3/6] nfs-utils: set IPV6_V6ONLY on nfssvc IPv6 sockets Jeff Layton
2009-05-26 15:15 ` [PATCH 4/6] nfs-utils: add IPv6 support to nfsd Jeff Layton
2009-05-26 15:24 ` Chuck Lever
2009-05-26 16:49 ` Jeff Layton
[not found] ` <20090526124907.4b711eaa-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-05-26 17:31 ` Chuck Lever
2009-05-26 17:56 ` Jeff Layton
2009-05-26 15:15 ` [PATCH 5/6] nfs-utils: limit protocols and families used by nfsd to those listed in /etc/netconfig Jeff Layton
2009-05-26 15:15 ` [PATCH 6/6] nfs-utils: add -4 and -6 options to nfsd manpage Jeff Layton
2009-05-26 15:24 ` [PATCH 0/6] nfs-utils: add IPv6 support for rpc.nfsd (try #2) Chuck Lever
2009-05-26 17:08 ` Jeff Layton
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=1243350951-13462-1-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=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