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/4] NFSv4.1: sp4_mach_cred cleanup (v2)
Date: Tue, 10 Sep 2013 18:44:29 -0400 [thread overview]
Message-ID: <1378853073-13256-1-git-send-email-dros@netapp.com> (raw)
Version 2 takes a new approach that Trond requested: we rely on the
cl_machine_cred to have a reference held for the life of the nfs_client
structure, so the sp4 stuff doesn't need to do any get/put_rpccred.
There's also two new patches:
- "fix SECINFO* use of put_rpccred" - recent changes (by me!) called
put_rpccred of rpc_message.rpc_cred, but this value can change when
nfs4_state_protect() is called. I searched through the rest of the client
source and couldn't find another place where this happens.
- WARN_ON -> WARN_ON_ONCE - oops.
Weston Andros Adamson (4):
NFSv4.1: sp4_mach_cred: ask for WRITE and COMMIT
NFSv4.1: fix SECINFO* use of put_rpccred
NFSv4.1: sp4_mach_cred: no need to ref count creds
NFSv4.1: sp4_mach_cred: WARN_ON -> WARN_ON_ONCE
fs/nfs/nfs4_fs.h | 10 +++++-----
fs/nfs/nfs4proc.c | 22 ++++++++++++++--------
2 files changed, 19 insertions(+), 13 deletions(-)
--
1.7.12.4 (Apple Git-37)
next reply other threads:[~2013-09-10 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 22:44 Weston Andros Adamson [this message]
2013-09-10 22:44 ` [PATCH 1/4] NFSv4.1: sp4_mach_cred: ask for WRITE and COMMIT Weston Andros Adamson
2013-09-10 22:44 ` [PATCH 2/4] NFSv4.1: fix SECINFO* use of put_rpccred Weston Andros Adamson
2013-09-10 22:44 ` [PATCH 3/4] NFSv4.1: sp4_mach_cred: no need to ref count creds Weston Andros Adamson
2013-09-11 13:01 ` Anna Schumaker
[not found] ` <CAFX2Jf=kbrS6byZBFOoZ64-rb9tCvUHDPZqkip3cy5K12FzaqQ@mail.gmail.com>
2013-09-11 13:13 ` Myklebust, Trond
2013-09-11 13:27 ` Anna Schumaker
2013-09-10 22:44 ` [PATCH 4/4] NFSv4.1: sp4_mach_cred: WARN_ON -> WARN_ON_ONCE 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=1378853073-13256-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).