From: Greg Banks <gnb@sgi.com>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: bfields@fieldses.org, neilb@suse.de, nfs@lists.sourceforge.net
Subject: Re: [RFC, PATCH 0/3] svc: gnb review cleanup for transport switch
Date: Thu, 11 Oct 2007 15:25:10 +1000 [thread overview]
Message-ID: <20071011052510.GD31422@sgi.com> (raw)
In-Reply-To: <20071011022356.3501.63859.stgit@dell3.ogc.int>
G'day,
Compendium reply.
On Wed, Oct 10, 2007 at 09:23:56PM -0500, Tom Tucker wrote:
> This patchset implements cleanup that is primarily driven by Greg Bank's
> review of the transport switch. A summary follows:
>
> - Fix the svc_create_xprt to properly allocate the temporary sockaddr storage
> necessary for IPv6.
>
> - Fix the svc_find_xprt service to lock the sv_permsocks list
>
> - Fix the svc_find_xprt service to handle the address family correctly
> when matching the port number on IPv6 connections.
>
> Thanks Greg.
>
> Other changes include:
>
> - Use the svc_find_xprt service to support adding and removing knfsd transports
> by writing strings to the /proc/fs/nfs/portlist file.
>
> Subject: [RFC,PATCH 1/3] svc: Change sockaddr to sockaddr_storage in
> svc_create_xprt
ok
> Subject: [RFC,PATCH 2/3] svc: Fix bugs in svc_find_xprt
ok
> Subject: [RFC,PATCH 3/3] knfsd: Modify write_ports to use
> svc_find_xprt service
ok by me, but Neil makes a good point about designing this interface
carefully.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
Apparently, I'm Bedevere. Which MPHG character are you?
I don't speak for SGI.
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-10-11 5:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 2:23 [RFC, PATCH 0/3] svc: gnb review cleanup for transport switch Tom Tucker
2007-10-11 2:28 ` [RFC, PATCH 1/3] svc: Change sockaddr to sockaddr_storage in svc_create_xprt Tom Tucker
2007-10-11 2:28 ` [RFC,PATCH 2/3] svc: Fix bugs in svc_find_xprt Tom Tucker
2007-10-11 2:29 ` [RFC, PATCH 3/3] knfsd: Modify write_ports to use svc_find_xprt service Tom Tucker
2007-10-11 3:00 ` Neil Brown
2007-10-11 3:46 ` J. Bruce Fields
2007-10-11 5:09 ` Neil Brown
2007-10-11 5:26 ` Greg Banks
2007-10-11 5:37 ` Neil Brown
2007-10-11 14:56 ` J. Bruce Fields
2007-10-11 5:11 ` Tom Tucker
2007-10-11 15:25 ` J. Bruce Fields
2007-10-11 15:27 ` Tom Tucker
2007-10-11 17:04 ` J. Bruce Fields
2007-10-11 5:25 ` Greg Banks [this message]
2007-10-11 17:09 ` [RFC, PATCH 0/3] svc: gnb review cleanup for transport switch J. Bruce Fields
2007-10-11 20:30 ` J. Bruce Fields
2007-10-11 20:53 ` Tom Tucker
2007-10-11 21:14 ` Tom Tucker
2007-10-11 22:04 ` Tom Tucker
2007-10-11 22:08 ` J. Bruce Fields
2007-10-12 15:17 ` Tom Tucker
2007-10-12 15:41 ` J. Bruce Fields
2007-10-12 16:27 ` Tom Tucker
2007-10-12 21:40 ` Tom Tucker
2007-10-12 22:03 ` J. Bruce Fields
2007-10-12 22:30 ` J. Bruce Fields
2007-10-13 3:48 ` J. Bruce Fields
2007-10-13 12:35 ` 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=20071011052510.GD31422@sgi.com \
--to=gnb@sgi.com \
--cc=bfields@fieldses.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=tom@opengridcomputing.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 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.