From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 3/3] NFSD: Enable NFS server use of PF_INET6
Date: Fri, 15 Jan 2010 17:35:19 -0500 [thread overview]
Message-ID: <20100115223519.GF30624@fieldses.org> (raw)
In-Reply-To: <20100113211048.19409.86029.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
On Wed, Jan 13, 2010 at 04:10:48PM -0500, Chuck Lever wrote:
> Try to use an PF_INET6 listener for NFSD if IPv6 is enabled in the
> kernel.
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>
> fs/nfsd/nfsctl.c | 36 +++++++++++++++++++++++++++++-------
> fs/nfsd/nfssvc.c | 27 ++++++++++++++++++++++-----
> 2 files changed, 51 insertions(+), 12 deletions(-)
>
> diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c
> index 2604c3e..7ebb7a5 100644
> --- a/fs/nfsd/nfsctl.c
> +++ b/fs/nfsd/nfsctl.c
> @@ -981,6 +981,26 @@ static ssize_t __write_ports_delfd(char *buf)
> return len;
> }
>
> +static ssize_t __write_ports_create_xprt(struct svc_serv *serv,
> + const char *transport,
> + const int family,
> + const unsigned short port)
> +{
> + int err;
> +
> + err = svc_create_xprt(serv, transport, family, port,
> + SVC_SOCK_ANONYMOUS);
> +
> + if (err < 0) {
> + /* Give a reasonable perror msg for bad transport string */
> + if (err == -ENOENT)
> + err = -EPROTONOSUPPORT;
I realize you're just moving this code, not writing it, so this is a
separate question, but: it looks like it's svc_create_xprt() itself that
chooses ENOENT for this case. Is there any reason it shouldn't just use
EPROTONOSUPPORT from the start?
--b.
next prev parent reply other threads:[~2010-01-15 22:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 21:10 [PATCH 0/3] NFSD IPv6 patches Chuck Lever
[not found] ` <20100113210650.19409.38009.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-13 21:10 ` [PATCH 1/3] SUNRPC: Use rpc_pton() in ip_map_parse() Chuck Lever
[not found] ` <20100113211031.19409.92550.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-15 22:25 ` J. Bruce Fields
2010-01-15 22:55 ` Chuck Lever
2010-01-15 22:58 ` J. Bruce Fields
2010-01-13 21:10 ` [PATCH 2/3] NFSD: Support AF_INET6 in svc_addsock() function Chuck Lever
2010-01-13 21:10 ` [PATCH 3/3] NFSD: Enable NFS server use of PF_INET6 Chuck Lever
[not found] ` <20100113211048.19409.86029.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-15 22:35 ` J. Bruce Fields [this message]
2010-01-15 23:09 ` Chuck Lever
2010-01-21 22:52 ` J. Bruce Fields
2010-01-22 17:10 ` Chuck Lever
2010-01-22 18:06 ` J. Bruce Fields
2010-01-15 22:44 ` J. Bruce Fields
2010-01-15 23:17 ` Chuck Lever
2010-01-21 22:07 ` J. Bruce Fields
2010-01-22 17:07 ` Chuck Lever
2010-01-22 18:06 ` J. Bruce Fields
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=20100115223519.GF30624@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.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