From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v4 0/6] nfsd: overhaul the client name tracking code
Date: Tue, 24 Jan 2012 18:10:09 -0500 [thread overview]
Message-ID: <20120124231009.GF12426@fieldses.org> (raw)
In-Reply-To: <1327348867-699-1-git-send-email-jlayton@redhat.com>
On Mon, Jan 23, 2012 at 03:01:01PM -0500, Jeff Layton wrote:
> - a number of the client_tracking functions have been changed to void
> return functions. Since the callers all ignore the return codes of those
> functions, there was little benefit in passing them back.
If you'd like to make that patch #1, I could apply it now.
--b.
>
> Comments and suggestions are welcome...
>
> Jeff Layton (6):
> nfsd: add nfsd4_client_tracking_ops struct and a way to set it
> sunrpc: create nfsd dir in rpc_pipefs
> nfsd: convert nfs4_client->cl_cb_flags to a generic flags field
> nfsd: add a header describing upcall to nfsdcld
> nfsd: add the infrastructure to handle the cld upcall
> nfsd: get boot generation number from upcall instead of boot_time
>
> fs/nfsd/nfs4callback.c | 12 +-
> fs/nfsd/nfs4recover.c | 480 +++++++++++++++++++++++++++++++++++++++++++++-
> fs/nfsd/nfs4state.c | 63 +++----
> fs/nfsd/state.h | 22 ++-
> include/linux/nfsd/cld.h | 58 ++++++
> net/sunrpc/rpc_pipe.c | 5 +
> 6 files changed, 581 insertions(+), 59 deletions(-)
> create mode 100644 include/linux/nfsd/cld.h
>
> --
> 1.7.7.5
>
prev parent reply other threads:[~2012-01-24 23:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 20:01 [PATCH v4 0/6] nfsd: overhaul the client name tracking code Jeff Layton
2012-01-23 20:01 ` [PATCH v4 1/6] nfsd: add nfsd4_client_tracking_ops struct and a way to set it Jeff Layton
2012-01-23 20:01 ` [PATCH v4 2/6] sunrpc: create nfsd dir in rpc_pipefs Jeff Layton
2012-01-23 20:01 ` [PATCH v4 3/6] nfsd: convert nfs4_client->cl_cb_flags to a generic flags field Jeff Layton
2012-01-23 20:01 ` [PATCH v4 4/6] nfsd: add a header describing upcall to nfsdcld Jeff Layton
2012-01-23 20:01 ` [PATCH v4 5/6] nfsd: add the infrastructure to handle the cld upcall Jeff Layton
2012-01-23 20:01 ` [PATCH v4 6/6] nfsd: get boot generation number from upcall instead of boot_time Jeff Layton
2012-01-24 23:08 ` [PATCH v4 0/6] nfsd: overhaul the client name tracking code J. Bruce Fields
2012-01-24 23:11 ` J. Bruce Fields
2012-01-25 11:41 ` Jeff Layton
2012-01-25 13:11 ` J. Bruce Fields
2012-01-25 13:38 ` Jeff Layton
2012-01-25 16:47 ` Chuck Lever
2012-01-25 17:14 ` J. Bruce Fields
2012-01-25 17:41 ` Chuck Lever
2012-01-25 18:55 ` J. Bruce Fields
2012-01-25 20:23 ` Jeff Layton
2012-01-25 21:25 ` J. Bruce Fields
2012-01-25 21:29 ` Chuck Lever
2012-01-25 21:54 ` J. Bruce Fields
2012-01-25 21:55 ` Chuck Lever
2012-01-25 22:11 ` J. Bruce Fields
2012-01-27 15:43 ` Jeff Layton
2012-01-25 20:29 ` Chuck Lever
2012-01-25 20:53 ` J. Bruce Fields
2012-01-25 21:08 ` Chuck Lever
2012-01-25 19:08 ` Jeff Layton
2012-01-24 23:10 ` J. Bruce Fields [this message]
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=20120124231009.GF12426@fieldses.org \
--to=bfields@fieldses.org \
--cc=jlayton@redhat.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 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.