From: Kinglong Mee <kinglongmee@gmail.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
kinglongmee@gmail.com
Subject: [PATCH 0/5 v3] Some updates and exclcreat supports
Date: Wed, 26 Aug 2015 21:09:50 +0800 [thread overview]
Message-ID: <55DDBA9E.1040008@gmail.com> (raw)
The first one is a bugfix, second is an update,
the last 3 are for supporting exclcreat.
v3,
Drop the first two patches that have be committed by Trond.
Fix the bad using of error value in nfs_setattr.
Kinglong Mee (5):
NFS: Check size by inode_newsize_ok in nfs_setattr
NFS: Make opened as optional argument in _nfs4_do_open
NFS: Update NFS4_BITMAP_SIZE
NFS: Get suppattr_exclcreat when getting server, capabilities
NFS: Send attributes in OPEN request for NFS4_CREATE_EXCLUSIVE4_1
fs/nfs/inode.c | 18 ++++++++--------
fs/nfs/nfs4file.c | 3 +--
fs/nfs/nfs4proc.c | 37 +++++++++++++++++++++++++--------
fs/nfs/nfs4xdr.c | 52 +++++++++++++++++++++++++++++++++++------------
include/linux/nfs_fs_sb.h | 5 +++++
include/linux/nfs_xdr.h | 4 +++-
include/uapi/linux/nfs4.h | 2 +-
7 files changed, 88 insertions(+), 33 deletions(-)
--
2.4.3
next reply other threads:[~2015-08-26 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 13:09 Kinglong Mee [this message]
2015-08-26 13:10 ` [PATCH 1/5 v3] NFS: Check size by inode_newsize_ok in nfs_setattr Kinglong Mee
2015-08-26 13:11 ` [PATCH 2/5 v3] NFS: Make opened as optional argument in _nfs4_do_open Kinglong Mee
2015-08-26 13:12 ` [PATCH 3/5 v3] NFS: Update NFS4_BITMAP_SIZE Kinglong Mee
2015-08-26 13:12 ` [PATCH 4/5 v3] NFS: Get suppattr_exclcreat when getting server capabilities Kinglong Mee
2015-08-26 13:13 ` [PATCH 5/5 v3] NFS: Send attributes in OPEN request for NFS4_CREATE_EXCLUSIVE4_1 Kinglong Mee
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=55DDBA9E.1040008@gmail.com \
--to=kinglongmee@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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.