From: Jeff Layton <jlayton@poochiereds.net>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Eric Van Hensbergen <ericvh@gmail.com>,
Ron Minnich <rminnich@sandia.gov>,
Latchesar Ionkov <lucho@ionkov.net>,
"Yan Zheng" <zyan@redhat.com>, Sage Weil <sage@redhat.com>,
Ilya Dryomov <idryomov@gmail.com>,
Steve French <sfrench@samba.org>,
Christine Caulfield <ccaulfie@redhat.com>,
David Teigland <teigland@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Steven Whitehouse <swhiteho@redhat.com>,
Bob Peterson <rpeterso@redhat.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Mark Fasheh <mfasheh@suse.com>, Joel Becker <jlbec@evilplan.org>,
aybuke ozdemir <aybuke.147@
Subject: Re: [PATCH V2 0/3] Minor cleanup for locks API
Date: Thu, 22 Oct 2015 14:45:33 -0400 [thread overview]
Message-ID: <20151022144533.5c8471bc@synchrony.poochiereds.net> (raw)
In-Reply-To: <cover.1445535305.git.bcodding@redhat.com>
On Thu, 22 Oct 2015 13:38:12 -0400
Benjamin Coddington <bcodding@redhat.com> wrote:
> NFS has recently been moving things around to cope with the situation where
> a struct file may not be available during an unlock. That work has
> presented an opportunity to do a minor cleanup on the locks API.
>
> Users of posix_lock_file_wait() (for FL_POSIX style locks) and
> flock_lock_file_wait() (for FL_FLOCK style locks) can instead call
> locks_lock_file_wait() for both lock types. Because the passed-in file_lock
> specifies its own type, the correct function can be selected on behalf of
> the user.
>
> This work allows further cleanup within NFS and lockd which will be
> submitted separately.
>
> Changes in v2:
> - fix typo that caused build failure for CONFIG_FILE_LOCKS=n
> - make posix_lock_inode_wait and flock_lock_inode_wait static
> - trimmed away a number of distro-lists to minimize cross-posting
>
> Benjamin Coddington (3):
> locks: introduce locks_lock_inode_wait()
> Move locks API users to locks_lock_inode_wait()
> locks: cleanup posix_lock_inode_wait and flock_lock_inode_wait
>
> drivers/staging/lustre/lustre/llite/file.c | 8 +----
> fs/9p/vfs_file.c | 4 +-
> fs/ceph/locks.c | 4 +-
> fs/cifs/file.c | 2 +-
> fs/dlm/plock.c | 4 +-
> fs/fuse/file.c | 2 +-
> fs/gfs2/file.c | 8 +++---
> fs/lockd/clntproc.c | 13 +---------
> fs/locks.c | 35 ++++++++++++++++++++++-----
> fs/nfs/file.c | 13 +---------
> fs/nfs/nfs4proc.c | 13 +---------
> fs/ocfs2/locks.c | 8 +++---
> include/linux/fs.h | 21 +++-------------
> 13 files changed, 53 insertions(+), 82 deletions(-)
>
Looks good to me too. I'll plan to merge them for v4.4.
Thanks!
--
Jeff Layton <jlayton@poochiereds.net>
prev parent reply other threads:[~2015-10-22 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 17:38 [PATCH V2 0/3] Minor cleanup for locks API Benjamin Coddington
2015-10-22 17:38 ` [PATCH V2 1/3] locks: introduce locks_lock_inode_wait() Benjamin Coddington
2015-10-22 17:38 ` [PATCH V2 2/3] Move locks API users to locks_lock_inode_wait() Benjamin Coddington
2015-10-22 17:38 ` [PATCH V2 3/3] locks: cleanup posix_lock_inode_wait and flock_lock_inode_wait Benjamin Coddington
2015-10-22 18:35 ` [PATCH V2 0/3] Minor cleanup for locks API J. Bruce Fields
2015-10-22 18:45 ` Jeff Layton [this message]
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=20151022144533.5c8471bc@synchrony.poochiereds.net \
--to=jlayton@poochiereds.net \
--cc=andreas.dilger@intel.com \
--cc=anna.schumaker@netapp.com \
--cc=bcodding@redhat.com \
--cc=bfields@fieldses.org \
--cc=ccaulfie@redhat.com \
--cc=ericvh@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=idryomov@gmail.com \
--cc=jlbec@evilplan.org \
--cc=lucho@ionkov.net \
--cc=mfasheh@suse.com \
--cc=miklos@szeredi.hu \
--cc=oleg.drokin@intel.com \
--cc=rminnich@sandia.gov \
--cc=rpeterso@redhat.com \
--cc=sage@redhat.com \
--cc=sfrench@samba.org \
--cc=swhiteho@redhat.com \
--cc=teigland@redhat.com \
--cc=trond.myklebust@primarydata.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zyan@redhat.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 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).