This patchset adds support for CB_NOTIFY_LOCK callbacks to the NFS
client. The basic idea is to add a waitqueue to the nfs_client and then
have blocking lock waiters wait on that queue for callbacks.
When a callback comes in, we use a keyed wakeup to wake any waiters. The
waitqueue handling is necessarily more "manual" than I would like, but I
don't see a real alternative there given that we need to insert the
waiters onto the waitqueue prior to sending the lock request, and
sending a lock request can involve blocking operations.
Tested in conjunction with the corresponding knfsd server-side patchset.
Jeff Layton (9):
nfs: the length argument to read_buf should be unsigned
nfs: eliminate pointless and confusing do_vfs_lock wrappers
nfs: check for POSIX lock capability on server even for flock locks
nfs: add a freezable_schedule_timeout_unsafe() and use it when waiting
to retry LOCK
nfs: add handling for CB_NOTIFY_LOCK in client
nfs: move nfs4_set_lock_state call into caller
nfs: add code to allow client to wait on lock callbacks
nfs: ensure that the filehandle in CB_NOTIFY_LOCK request matches the
inode
nfs: track whether server sets MAY_NOTIFY_LOCK flag
fs/nfs/callback.h | 8 ++++
fs/nfs/callback_proc.c | 20 ++++++++
fs/nfs/callback_xdr.c | 51 +++++++++++++++++++-
fs/nfs/file.c | 9 +---
fs/nfs/nfs4_fs.h | 1 +
fs/nfs/nfs4client.c | 1 +
fs/nfs/nfs4proc.c | 118 +++++++++++++++++++++++++++++++++++++---------
include/linux/freezer.h | 13 +++++
include/linux/nfs_fs_sb.h | 1 +
9 files changed, 190 insertions(+), 32 deletions(-)
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
