Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: okir@suse.de, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] SUNRPC: Register both netids for AF_INET6 servers
Date: Fri, 26 Sep 2008 17:17:36 -0400	[thread overview]
Message-ID: <20080926211736.GA7138@fieldses.org> (raw)
In-Reply-To: <20080915212723.3939.23359.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>

On Mon, Sep 15, 2008 at 04:27:23PM -0500, Chuck Lever wrote:
...
> We've recently determined that this is incorrect behavior.  In the
> TI-RPC world, "udp6" is not meant to imply that the registered RPC
> service handles requests from AF_INET as well, even if the listener
> socket does address mapping.  "udp" and "udp6" are entirely separate
> capabilities, and must be registered separately.
> 
> The Linux kernel, unlike TI-RPC, leverages address mapping to allow a
> single listener socket to handle requests for both AF_INET and AF_INET6.
> This is still OK, but the kernel currently assumes registering "udp6"
> will cover "udp" as well.  It registers only "udp6" for it's AF_INET6
> services, even though they handle both AF_INET and AF_INET6 on the same
> port.
> 
> So svc_register() actually needs to register both "udp" and "udp6"
> explicitly (and likewise for TCP).  Until rpcbind is fixed, the
> kernel can ignore the return code for the second RPCB_SET call.

Looks fine, thanks, applied.

> Please merge this with commit 15231312:
> 
>     SUNRPC: Support IPv6 when registering kernel RPC services

That was actually a pretty helpful commit message; I'm tempted just to
leave this unmerged and not worry too much about the briefly-existing
bug in this case.

--b.

  parent reply	other threads:[~2008-09-26 21:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15 21:27 [PATCH 0/2] Fix-ups for 2.6.28 rpcb kernel support Chuck Lever
     [not found] ` <20080915212437.3939.82594.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-09-15 21:27   ` [PATCH 1/2] SUNRPC: Register both netids for AF_INET6 servers Chuck Lever
     [not found]     ` <20080915212723.3939.23359.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-09-26 21:17       ` J. Bruce Fields [this message]
2008-09-15 21:27   ` [PATCH 2/2] SUNRPC: Use short-hand IPv6 ANYADDR for RPCB_SET Chuck Lever
     [not found]     ` <20080915212730.3939.35770.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-09-26 21:20       ` J. Bruce Fields
2008-09-26 21:37         ` Chuck Lever

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=20080926211736.GA7138@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=okir@suse.de \
    /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