From: schumaker.anna@gmail.com
To: Trond.Myklebust@primarydata.com, linux-nfs@vger.kernel.org
Subject: [PATCH 0/5] NFS: A few small NFSv4 cleanups
Date: Fri, 4 May 2018 16:22:47 -0400 [thread overview]
Message-ID: <20180504202252.5862-1-Anna.Schumaker@Netapp.com> (raw)
From: Anna Schumaker <Anna.Schumaker@Netapp.com>
These patches are a few cleanups I noticed while poking through the
code. The first two move calls to nfs4_state_protect() into the v4
module and the last three are cleanups to the nfs4_call_sync() process.
Thoughts?
Anna
Anna Schumaker (5):
NFS: Move call to nfs4_state_protect_write() to nfs4_write_setup()
NFS: Move call to nfs4_state_protect() to nfs4_commit_setup()
NFS: Pass "privileged" value to nfs4_init_sequence()
NFS: Pass "privileged" value to nfs4_call_sync()
NFS: Combine nfs4_call_sync() with nfs4_call_sync_sequence()
fs/nfs/nfs3proc.c | 6 +-
fs/nfs/nfs42proc.c | 10 +--
fs/nfs/nfs4_fs.h | 4 +-
fs/nfs/nfs4proc.c | 174 +++++++++++++++++-----------------------
fs/nfs/proc.c | 6 +-
fs/nfs/write.c | 10 +--
include/linux/nfs_xdr.h | 6 +-
7 files changed, 94 insertions(+), 122 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-04 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 20:22 schumaker.anna [this message]
2018-05-04 20:22 ` [PATCH 1/5] NFS: Move call to nfs4_state_protect_write() to nfs4_write_setup() schumaker.anna
2018-05-04 20:22 ` [PATCH 2/5] NFS: Move call to nfs4_state_protect() to nfs4_commit_setup() schumaker.anna
2018-05-04 20:22 ` [PATCH 3/5] NFS: Pass "privileged" value to nfs4_init_sequence() schumaker.anna
2018-05-04 20:22 ` [PATCH 4/5] NFS: Pass "privileged" value to nfs4_call_sync() schumaker.anna
2018-05-29 13:52 ` Trond Myklebust
2018-05-04 20:22 ` [PATCH 5/5] NFS: Combine nfs4_call_sync() with nfs4_call_sync_sequence() schumaker.anna
2018-05-29 13:45 ` Trond Myklebust
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=20180504202252.5862-1-Anna.Schumaker@Netapp.com \
--to=schumaker.anna@gmail.com \
--cc=Trond.Myklebust@primarydata.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.