From: "J. Bruce Fields" <bfields@fieldses.org>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
jlayton@redhat.com, Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH 00/13] Implement NFSv4 delegations, take 12
Date: Wed, 2 Oct 2013 09:54:23 -0400 [thread overview]
Message-ID: <20131002135423.GA14808@fieldses.org> (raw)
In-Reply-To: <1379623837-30798-1-git-send-email-bfields@redhat.com>
On Thu, Sep 19, 2013 at 04:50:24PM -0400, J. Bruce Fields wrote:
> From: "J. Bruce Fields" <bfields@redhat.com>
>
> Al, if you don't see any objections, could you queue this up for 3.13?
Note: if it's more convenient, the identical patches are also available
from
git://linux-nfs.org/~bfields/linux.git for-viro
--b.
>
> Changes since version 11:
> - rebase to 3.12-rc1
> - fix to lock class in single-lock case of
> lock_two_nondirectories
>
> Changes since version 10:
> - appended Jeff's fix for a setlease/open race (otherwise
> unrelated to this series, but there are some minor conficts to
> resolve).
>
> Changes since version 9:
> - just a rebase to 3.11-rc6
>
> Changes since version 8:
> - additional warnings in lock_two_nondirectories
> - lock_two_nondirectories handles NULL second argument,
> simplifying vfs_rename_other
> - kerneldoc comments on notify_change, vfs_link, vfs_rename,
> vfs_unlink, to explain delegated_inode argument.
> - make clear non-support of write delegations in
> generic_add_lease
> - rebase to 3.11-rc1
>
> Introduction copied from previous posting:
>
> This patch series implements read delegations, which allow NFSv4 clients
> to perform read opens without contacting the server, by promising to
> call back to clients before modifying the data, metadata, or set of
> links pointing to a file.
>
> The main recent change was in response to review from Linus, who didn't
> want us to hang under directory i_mutex's on timeouts communicating with
> unresponsive clients.
>
> So, this version of the series drops the i_mutex before waiting. The
> logic ends up looking something like:
>
> acquire locks
> look up inode
> test for delegation; if found:
> take reference on inode
> release locks
> wait for delegation break
> drop reference on inode
> retry
>
> The initial test for a delegation happens after the lock on the
> delegated inode is acquired, but additional directory mutexes may have
> been acquired further up the call stack. I therefore add a "struct
> inode **" argument to any intervening functions, which we use to pass
> the inode back up to the caller in the case it needs to wait for the
> delegation to be broken.
>
> I also allow callers to pass in NULL for the "struct inode **" argument
> to indicate they'd rather just fail than wait for a delegation. For
> example, as long as ecryptfs isn't exportable I assume they'd rather not
> see retry logic there that they won't use. But I may have misjudged in
> some of these cases.
>
> J. Bruce Fields (12):
> vfs: pull ext4's double-i_mutex-locking into common code
> vfs: don't use PARENT/CHILD lock classes for non-directories
> vfs: rename I_MUTEX_QUOTA now that it's not used for quotas
> vfs: take i_mutex on renamed file
> locks: introduce new FL_DELEG lock flag
> locks: implement delegations
> namei: minor vfs_unlink cleanup
> locks: break delegations on unlink
> locks: helper functions for delegation breaking
> locks: break delegations on rename
> locks: break delegations on link
> locks: break delegations on any attribute modification
>
> Jeff Layton (1):
> locks: close potential race between setlease and open
>
> Documentation/filesystems/directory-locking | 31 ++++--
> drivers/base/devtmpfs.c | 6 +-
> fs/attr.c | 25 ++++-
> fs/cachefiles/interface.c | 4 +-
> fs/cachefiles/namei.c | 4 +-
> fs/ecryptfs/inode.c | 6 +-
> fs/ext4/ext4.h | 2 -
> fs/ext4/ioctl.c | 4 +-
> fs/ext4/move_extent.c | 40 +-------
> fs/hpfs/namei.c | 2 +-
> fs/inode.c | 42 ++++++++-
> fs/locks.c | 130 +++++++++++++++++++++-----
> fs/namei.c | 135 +++++++++++++++++++++++----
> fs/nfsd/nfs4state.c | 2 +-
> fs/nfsd/vfs.c | 14 ++-
> fs/open.c | 22 ++++-
> fs/utimes.c | 9 +-
> include/linux/fs.h | 78 +++++++++++++---
> ipc/mqueue.c | 2 +-
> 19 files changed, 428 insertions(+), 130 deletions(-)
>
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "J. Bruce Fields" <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
To: "J. Bruce Fields" <bfields-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Dave Chinner <david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org>
Subject: Re: [PATCH 00/13] Implement NFSv4 delegations, take 12
Date: Wed, 2 Oct 2013 09:54:23 -0400 [thread overview]
Message-ID: <20131002135423.GA14808@fieldses.org> (raw)
In-Reply-To: <1379623837-30798-1-git-send-email-bfields-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Thu, Sep 19, 2013 at 04:50:24PM -0400, J. Bruce Fields wrote:
> From: "J. Bruce Fields" <bfields-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>
> Al, if you don't see any objections, could you queue this up for 3.13?
Note: if it's more convenient, the identical patches are also available
from
git://linux-nfs.org/~bfields/linux.git for-viro
--b.
>
> Changes since version 11:
> - rebase to 3.12-rc1
> - fix to lock class in single-lock case of
> lock_two_nondirectories
>
> Changes since version 10:
> - appended Jeff's fix for a setlease/open race (otherwise
> unrelated to this series, but there are some minor conficts to
> resolve).
>
> Changes since version 9:
> - just a rebase to 3.11-rc6
>
> Changes since version 8:
> - additional warnings in lock_two_nondirectories
> - lock_two_nondirectories handles NULL second argument,
> simplifying vfs_rename_other
> - kerneldoc comments on notify_change, vfs_link, vfs_rename,
> vfs_unlink, to explain delegated_inode argument.
> - make clear non-support of write delegations in
> generic_add_lease
> - rebase to 3.11-rc1
>
> Introduction copied from previous posting:
>
> This patch series implements read delegations, which allow NFSv4 clients
> to perform read opens without contacting the server, by promising to
> call back to clients before modifying the data, metadata, or set of
> links pointing to a file.
>
> The main recent change was in response to review from Linus, who didn't
> want us to hang under directory i_mutex's on timeouts communicating with
> unresponsive clients.
>
> So, this version of the series drops the i_mutex before waiting. The
> logic ends up looking something like:
>
> acquire locks
> look up inode
> test for delegation; if found:
> take reference on inode
> release locks
> wait for delegation break
> drop reference on inode
> retry
>
> The initial test for a delegation happens after the lock on the
> delegated inode is acquired, but additional directory mutexes may have
> been acquired further up the call stack. I therefore add a "struct
> inode **" argument to any intervening functions, which we use to pass
> the inode back up to the caller in the case it needs to wait for the
> delegation to be broken.
>
> I also allow callers to pass in NULL for the "struct inode **" argument
> to indicate they'd rather just fail than wait for a delegation. For
> example, as long as ecryptfs isn't exportable I assume they'd rather not
> see retry logic there that they won't use. But I may have misjudged in
> some of these cases.
>
> J. Bruce Fields (12):
> vfs: pull ext4's double-i_mutex-locking into common code
> vfs: don't use PARENT/CHILD lock classes for non-directories
> vfs: rename I_MUTEX_QUOTA now that it's not used for quotas
> vfs: take i_mutex on renamed file
> locks: introduce new FL_DELEG lock flag
> locks: implement delegations
> namei: minor vfs_unlink cleanup
> locks: break delegations on unlink
> locks: helper functions for delegation breaking
> locks: break delegations on rename
> locks: break delegations on link
> locks: break delegations on any attribute modification
>
> Jeff Layton (1):
> locks: close potential race between setlease and open
>
> Documentation/filesystems/directory-locking | 31 ++++--
> drivers/base/devtmpfs.c | 6 +-
> fs/attr.c | 25 ++++-
> fs/cachefiles/interface.c | 4 +-
> fs/cachefiles/namei.c | 4 +-
> fs/ecryptfs/inode.c | 6 +-
> fs/ext4/ext4.h | 2 -
> fs/ext4/ioctl.c | 4 +-
> fs/ext4/move_extent.c | 40 +-------
> fs/hpfs/namei.c | 2 +-
> fs/inode.c | 42 ++++++++-
> fs/locks.c | 130 +++++++++++++++++++++-----
> fs/namei.c | 135 +++++++++++++++++++++++----
> fs/nfsd/nfs4state.c | 2 +-
> fs/nfsd/vfs.c | 14 ++-
> fs/open.c | 22 ++++-
> fs/utimes.c | 9 +-
> include/linux/fs.h | 78 +++++++++++++---
> ipc/mqueue.c | 2 +-
> 19 files changed, 428 insertions(+), 130 deletions(-)
>
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-10-02 13:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 20:50 [PATCH 00/13] Implement NFSv4 delegations, take 12 J. Bruce Fields
2013-09-19 20:50 ` J. Bruce Fields
2013-09-19 20:50 ` [PATCH 01/13] vfs: pull ext4's double-i_mutex-locking into common code J. Bruce Fields
2013-09-19 20:50 ` [PATCH 02/13] vfs: don't use PARENT/CHILD lock classes for non-directories J. Bruce Fields
2013-09-19 20:50 ` [PATCH 03/13] vfs: rename I_MUTEX_QUOTA now that it's not used for quotas J. Bruce Fields
2013-09-19 20:50 ` [PATCH 04/13] vfs: take i_mutex on renamed file J. Bruce Fields
2013-09-19 20:50 ` [PATCH 05/13] locks: introduce new FL_DELEG lock flag J. Bruce Fields
2013-09-19 20:50 ` J. Bruce Fields
2013-09-19 20:50 ` [PATCH 06/13] locks: implement delegations J. Bruce Fields
2013-09-19 20:50 ` J. Bruce Fields
2013-09-19 20:50 ` [PATCH 07/13] namei: minor vfs_unlink cleanup J. Bruce Fields
2013-09-19 20:50 ` [PATCH 08/13] locks: break delegations on unlink J. Bruce Fields
2013-09-19 20:50 ` J. Bruce Fields
2013-09-19 20:50 ` [PATCH 09/13] locks: helper functions for delegation breaking J. Bruce Fields
2013-09-19 20:50 ` [PATCH 10/13] locks: break delegations on rename J. Bruce Fields
2013-09-19 20:50 ` [PATCH 11/13] locks: break delegations on link J. Bruce Fields
2013-09-19 20:50 ` [PATCH 12/13] locks: break delegations on any attribute modification J. Bruce Fields
2013-09-19 20:50 ` J. Bruce Fields
2013-09-19 20:50 ` [PATCH 13/13] locks: close potential race between setlease and open J. Bruce Fields
2013-10-02 13:54 ` J. Bruce Fields [this message]
2013-10-02 13:54 ` [PATCH 00/13] Implement NFSv4 delegations, take 12 J. Bruce Fields
2013-10-02 20:16 ` J. Bruce Fields
2013-10-02 20:16 ` J. Bruce Fields
2013-10-03 19:41 ` J. Bruce Fields
2013-10-07 15:20 ` J. Bruce Fields
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=20131002135423.GA14808@fieldses.org \
--to=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=david@fromorbit.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.