From: Benjamin Coddington <bcodding@redhat.com>
To: Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Latchesar Ionkov <lucho@ionkov.net>,
linux-fsdevel@vger.kernel.org,
Trond Myklebust <trond.myklebust@primarydata.com>,
devel@driverdev.osuosl.org, Yan Zheng <zyan@redhat.com>,
cluster-devel@redhat.com, Sage Weil <sage@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Christoph Hellwig <hch@infradead.org>,
fuse-devel@lists.sourceforge.net,
Christine Caulfield <ccaulfie@redhat.com>,
v9fs-developer@lists.sourceforge.net,
Ilya Dryomov <idryomov@gmail.com>,
linux-cifs@vger.kernel.org,
Eric Van Hensbergen <ericvh@gmail.com>,
Mark Fasheh <mfasheh@suse.com>,
Oleg Drokin <oleg.drokin@intel.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
David Teigland <teigland@redhat.com>,
Joel Becker <jlbec@evilplan.org>,
ceph-devel@vger.kernel.org, Abdul Hussain <habdul@visteon.com>,
Steven Whitehouse <swhiteho@redhat.com>,
linux-nfs@vger.kernel.org,
Andreas Dilger <andreas.dilger@intel.com>,
Greg K
Subject: [PATCH 0/3] Minor cleanup for locks API
Date: Thu, 22 Oct 2015 11:35:53 -0400 [thread overview]
Message-ID: <cover.1445524157.git.bcodding@redhat.com> (raw)
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.
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 | 31 +++++++++++++++++++++++----
fs/nfs/file.c | 13 +----------
fs/nfs/nfs4proc.c | 13 +----------
fs/ocfs2/locks.c | 8 +++---
include/linux/fs.h | 21 +++---------------
13 files changed, 51 insertions(+), 80 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Coddington <bcodding@redhat.com>
To: Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
Alexander Viro <viro@zeniv.linux.org.uk>
Cc: 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@gmail.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Abdul Hussain <habdul@visteon.com>,
lustre-devel@lists.lustre.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net, ceph-devel@vger.kernel.org,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
cluster-devel@redhat.com, fuse-devel@lists.sourceforge.net,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
ocfs2-devel@oss.oracle.com
Subject: [PATCH 0/3] Minor cleanup for locks API
Date: Thu, 22 Oct 2015 11:35:53 -0400 [thread overview]
Message-ID: <cover.1445524157.git.bcodding@redhat.com> (raw)
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.
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 | 31 +++++++++++++++++++++++----
fs/nfs/file.c | 13 +----------
fs/nfs/nfs4proc.c | 13 +----------
fs/ocfs2/locks.c | 8 +++---
include/linux/fs.h | 21 +++---------------
13 files changed, 51 insertions(+), 80 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Coddington <bcodding@redhat.com>
To: Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Latchesar Ionkov <lucho@ionkov.net>,
linux-fsdevel@vger.kernel.org,
Trond Myklebust <trond.myklebust@primarydata.com>,
devel@driverdev.osuosl.org, Yan Zheng <zyan@redhat.com>,
cluster-devel@redhat.com, Sage Weil <sage@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Christoph Hellwig <hch@infradead.org>,
fuse-devel@lists.sourceforge.net,
Christine Caulfield <ccaulfie@redhat.com>,
v9fs-developer@lists.sourceforge.net,
Ilya Dryomov <idryomov@gmail.com>,
linux-cifs@vger.kernel.org,
Eric Van Hensbergen <ericvh@gmail.com>,
Mark Fasheh <mfasheh@suse.com>,
Oleg Drokin <oleg.drokin@intel.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
David Teigland <teigland@redhat.com>,
Joel Becker <jlbec@evilplan.org>,
ceph-devel@vger.kernel.org, Abdul Hussain <habdul@visteon.com>,
Steven Whitehouse <swhiteho@redhat.com>,
linux-nfs@vger.kernel.org,
Andreas Dilger <andreas.dilger@intel.com>,
Greg
Subject: [PATCH 0/3] Minor cleanup for locks API
Date: Thu, 22 Oct 2015 11:35:53 -0400 [thread overview]
Message-ID: <cover.1445524157.git.bcodding@redhat.com> (raw)
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.
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 | 31 +++++++++++++++++++++++----
fs/nfs/file.c | 13 +----------
fs/nfs/nfs4proc.c | 13 +----------
fs/ocfs2/locks.c | 8 +++---
include/linux/fs.h | 21 +++---------------
13 files changed, 51 insertions(+), 80 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Coddington <bcodding@redhat.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH 0/3] Minor cleanup for locks API
Date: Thu, 22 Oct 2015 11:35:53 -0400 [thread overview]
Message-ID: <cover.1445524157.git.bcodding@redhat.com> (raw)
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.
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 | 31 +++++++++++++++++++++++----
fs/nfs/file.c | 13 +----------
fs/nfs/nfs4proc.c | 13 +----------
fs/ocfs2/locks.c | 8 +++---
include/linux/fs.h | 21 +++---------------
13 files changed, 51 insertions(+), 80 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Coddington <bcodding@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/3] Minor cleanup for locks API
Date: Thu, 22 Oct 2015 11:35:53 -0400 [thread overview]
Message-ID: <cover.1445524157.git.bcodding@redhat.com> (raw)
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.
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 | 31 +++++++++++++++++++++++----
fs/nfs/file.c | 13 +----------
fs/nfs/nfs4proc.c | 13 +----------
fs/ocfs2/locks.c | 8 +++---
include/linux/fs.h | 21 +++---------------
13 files changed, 51 insertions(+), 80 deletions(-)
next reply other threads:[~2015-10-22 15:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 15:35 Benjamin Coddington [this message]
2015-10-22 15:35 ` [Cluster-devel] [PATCH 0/3] Minor cleanup for locks API Benjamin Coddington
2015-10-22 15:35 ` [lustre-devel] " Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 15:35 ` [PATCH 1/3] locks: introduce locks_lock_inode_wait() Benjamin Coddington
2015-10-22 15:35 ` [Cluster-devel] " Benjamin Coddington
2015-10-22 15:35 ` [lustre-devel] " Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
[not found] ` <daf0d3941f34438c1fbdc94a5f3a47c2b22f3ee8.1445524157.git.bcodding-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-22 15:59 ` kbuild test robot
2015-10-22 15:59 ` [Cluster-devel] " kbuild test robot
2015-10-22 15:59 ` [lustre-devel] " kbuild test robot
2015-10-22 15:59 ` kbuild test robot
2015-10-22 16:21 ` Benjamin Coddington
2015-10-22 16:21 ` [Cluster-devel] " Benjamin Coddington
2015-10-22 16:21 ` [lustre-devel] " Benjamin Coddington
2015-10-22 16:21 ` Benjamin Coddington
2015-10-22 16:21 ` Benjamin Coddington
2015-10-22 15:35 ` [PATCH 2/3] Move locks API users to locks_lock_inode_wait() Benjamin Coddington
2015-10-22 15:35 ` [Cluster-devel] " Benjamin Coddington
2015-10-22 15:35 ` [lustre-devel] " Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 15:35 ` [PATCH 3/3] locks: cleanup posix_lock_inode_wait and flock_lock_inode_wait Benjamin Coddington
2015-10-22 15:35 ` [Cluster-devel] " Benjamin Coddington
2015-10-22 15:35 ` [lustre-devel] " Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 16:36 ` [RFC PATCH] locks: posix_lock_inode_wait() can be static kbuild test robot
2015-10-22 16:36 ` [Cluster-devel] " kbuild test robot
2015-10-22 16:36 ` [lustre-devel] " kbuild test robot
2015-10-22 16:36 ` kbuild test robot
2015-10-22 16:36 ` [PATCH 3/3] locks: cleanup posix_lock_inode_wait and flock_lock_inode_wait kbuild test robot
2015-10-22 16:36 ` [Cluster-devel] " kbuild test robot
2015-10-22 16:36 ` [lustre-devel] " kbuild test robot
2015-10-22 16:36 ` kbuild test robot
2015-10-22 16:36 ` kbuild test robot
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=cover.1445524157.git.bcodding@redhat.com \
--to=bcodding@redhat.com \
--cc=Julia.Lawall@lip6.fr \
--cc=andreas.dilger@intel.com \
--cc=bfields@fieldses.org \
--cc=ccaulfie@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=cluster-devel@redhat.com \
--cc=devel@driverdev.osuosl.org \
--cc=ericvh@gmail.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=habdul@visteon.com \
--cc=hch@infradead.org \
--cc=idryomov@gmail.com \
--cc=jlayton@poochiereds.net \
--cc=jlbec@evilplan.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=mfasheh@suse.com \
--cc=miklos@szeredi.hu \
--cc=oleg.drokin@intel.com \
--cc=sage@redhat.com \
--cc=swhiteho@redhat.com \
--cc=teigland@redhat.com \
--cc=trond.myklebust@primarydata.com \
--cc=v9fs-developer@lists.sourceforge.net \
--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 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.