linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] nfsd: bugfixes for
Date: Mon,  5 Mar 2012 11:42:34 -0500	[thread overview]
Message-ID: <1330965756-24180-1-git-send-email-jlayton@redhat.com> (raw)

These patches are a couple of bugfixes for some problems I noticed
while working on the nfsdcld patches. Bruce asked that I break them
out separately and rebase the rest of the set on top.

I've tested earlier patchsets with similar changes, but have not
heavily tested these individually. Unfortunately, I might not get to
it for a little while.

Jeff Layton (2):
  nfsd: convert nfs4_client->cl_cb_flags to a generic flags field
  nfsd: only initialize client tracking if nfs4_state_start is
    successful

 fs/nfsd/nfs4callback.c |   14 +++++-----
 fs/nfsd/nfs4proc.c     |    3 +-
 fs/nfsd/nfs4recover.c  |    7 ++---
 fs/nfsd/nfs4state.c    |   64 ++++++++++++++++++++++++++++++------------------
 fs/nfsd/state.h        |   11 +++++---
 5 files changed, 59 insertions(+), 40 deletions(-)

-- 
1.7.7.6


             reply	other threads:[~2012-03-05 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 16:42 Jeff Layton [this message]
2012-03-05 16:42 ` [PATCH 1/2] nfsd: convert nfs4_client->cl_cb_flags to a generic flags field Jeff Layton
2012-03-06 20:11   ` J. Bruce Fields
2012-03-06 20:14     ` J. Bruce Fields
2012-03-06 20:35       ` Jeff Layton
2012-03-06 23:14       ` J. Bruce Fields
2012-03-05 16:42 ` [PATCH 2/2] nfsd: only initialize client tracking if nfs4_state_start is successful Jeff Layton

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=1330965756-24180-1-git-send-email-jlayton@redhat.com \
    --to=jlayton@redhat.com \
    --cc=bfields@fieldses.org \
    --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;
as well as URLs for NNTP newsgroup(s).