All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Tucker <tom@opengridcomputing.com>
To: Greg Banks <gnb@sgi.com>
Cc: neilb@suse.de, bfields@fieldses.org, nfs@lists.sourceforge.net
Subject: Re: [RFC, PATCH] svc: Modify svc_create_xprt to return local port
Date: Tue, 09 Oct 2007 21:28:17 -0500	[thread overview]
Message-ID: <1191983297.16714.14.camel@trinity.ogc.int> (raw)
In-Reply-To: <20071010023540.GB20690@sgi.com>

On Wed, 2007-10-10 at 12:35 +1000, Greg Banks wrote:
> On Tue, Oct 09, 2007 at 05:52:53PM -0500, Tom Tucker wrote:
> > 
> > Please take this version of the patch. The previous version has a
> > whitespace issue. Sorry for the inconvenience.
> > 
> > This patch fixes a regression introduced by the svc transport
> > switch as follows:
> > 
> > - Listening endpoints need to have their local address set properly. 
> > 
> > - svc_create_xprt needs to return the local port number since the
> >   the nfs4 callback service uses the return value to determine the 
> >   local port elected by the transport when binding to zero.
> > 
> > [...]
> > --- a/net/sunrpc/svcsock.c
> > +++ b/net/sunrpc/svcsock.c
> > @@ -1278,6 +1278,8 @@ svc_create_socket(struct svc_serv *serv,
> >  	int		error;
> >  	int		type;
> >  	char		buf[RPC_MAX_ADDRBUFLEN];
> > +	struct sockaddr	newsin;
> > +	int		newlen;
> 
> Struct sockaddr isn't big enough for this to work with ipv6,
> use struct sockaddr_storage.  Or do the kernel_getsockname()
> driectly into xprt->xpt_local.

I think this is preferred. Thanks Greg.

> 
> Greg.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-10-10  2:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 22:52 [RFC, PATCH] svc: Modify svc_create_xprt to return local port Tom Tucker
2007-10-10  2:35 ` Greg Banks
2007-10-10  2:28   ` Tom Tucker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-09 22:47 Tom Tucker

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=1191983297.16714.14.camel@trinity.ogc.int \
    --to=tom@opengridcomputing.com \
    --cc=bfields@fieldses.org \
    --cc=gnb@sgi.com \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.