linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Weston Andros Adamson <dros@netapp.com>
To: <Trond.Myklebust@netapp.com>
Cc: <linux-nfs@vger.kernel.org>, Weston Andros Adamson <dros@netapp.com>
Subject: [PATCH 0/2] NFSv4.1: sp4_mach_cred cleanup
Date: Tue, 10 Sep 2013 14:55:56 -0400	[thread overview]
Message-ID: <1378839358-10389-1-git-send-email-dros@netapp.com> (raw)

These two patches do some final cleanup of SP4_MACH_CRED:
  - actually call put_rpccred() if we get_rpccred(clp->cl_machine_cred)
  - advertise to server that we support WRITE and COMMIT

Tested against a linux nfsd hacked to "support" sp4_mach_cred for the
client supported ops.  Also tested building with v4.1 disabled and v4 disabled.

Trond - it's (obviously) up to you if these get in during this merge window.
I think they're pretty straightforward.  Also, these patches are independent
from eachother, so it's ok to select one but not the other.


Weston Andros Adamson (2):
  NFSv4.1: clean up after using machine cred
  NFSv4.1: sp4_mach_cred: ask for WRITE and COMMIT

 fs/nfs/nfs4_fs.h  | 58 ++++++++++++++++++++++++++++++++++++-------------------
 fs/nfs/nfs4proc.c | 58 +++++++++++++++++++++++++++++++++++++------------------
 fs/nfs/write.c    | 18 +++++++++++------
 3 files changed, 89 insertions(+), 45 deletions(-)

-- 
1.7.12.4 (Apple Git-37)


             reply	other threads:[~2013-09-10 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 18:55 Weston Andros Adamson [this message]
2013-09-10 18:55 ` [PATCH 1/2] NFSv4.1: clean up after using machine cred Weston Andros Adamson
2013-09-10 19:31   ` Myklebust, Trond
2013-09-10 21:08     ` Adamson, Dros
2013-09-10 21:53       ` Myklebust, Trond
2013-09-10 18:55 ` [PATCH 2/2] NFSv4.1: sp4_mach_cred: ask for WRITE and COMMIT Weston Andros Adamson

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=1378839358-10389-1-git-send-email-dros@netapp.com \
    --to=dros@netapp.com \
    --cc=Trond.Myklebust@netapp.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 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).