From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
switeho@redhat.com, Trond.Myklebust@netapp.com,
Marc Eshel <eshel@almaden.ibm.com>,
richterd@citi.umich.edu, Christoph Hellwig <hch@infradead.org>
Subject: Re: lease and lock patches
Date: Wed, 18 Jul 2007 19:22:55 -0400 [thread overview]
Message-ID: <20070718232255.GO7111@fieldses.org> (raw)
In-Reply-To: <20070713233457.GA6552@fieldses.org>
Would it still be possible to merge this for 2.6.23? They've been
through linux-fsdevel, Christoph has taken a pass through them, and I
don't know of any unaddressed problems.
--b.
On Fri, Jul 13, 2007 at 07:34:57PM -0400, J. Bruce Fields wrote:
> Please pull from the 'for-linus' branch at
>
> git://linux-nfs.org/~bfields/linux.git for-linus
>
> for a series of patches which add a setlease() file method. The
> longer-term goal is to allow cluster and network filesystems to give out
> consistent leases when possible, in particular to allow nfsd to give out
> delegations on cluster filesystems. For now, though, we're using this
> just to disallow leases selectively on certain filesystems (nfs and gfs2
> for now) where they don't make sense.
>
> Also includes some minor locks.c cleanup.
>
> J. Bruce Fields (9):
> locks: convert an -EINVAL return to a BUG
> locks: clean up lease_alloc()
> locks: share more common lease code
> locks: rename lease functions to reflect locks.c conventions
> locks: provide a file lease method enabling cluster-coherent leases
> locks: export setlease to filesystems
> nfs: disable leases over NFS
> locks: make posix_test_lock() interface more consistent
> locks: fix vfs_test_lock() comment
>
> Marc Eshel (1):
> gfs2: stop giving out non-cluster-coherent leases
>
> david m. richter (1):
> leases: minor break_lease() comment clarification
>
> fs/gfs2/ops_file.c | 24 +++++++++++
> fs/locks.c | 112 ++++++++++++++++++++++++++------------------------
> fs/nfs/file.c | 16 +++++++-
> fs/nfsd/nfs4state.c | 10 ++--
> include/linux/fs.h | 4 +-
> 5 files changed, 105 insertions(+), 61 deletions(-)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2007-07-18 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 23:34 lease and lock patches J. Bruce Fields
2007-07-18 23:22 ` J. Bruce Fields [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=20070718232255.GO7111@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=eshel@almaden.ibm.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=richterd@citi.umich.edu \
--cc=switeho@redhat.com \
--cc=torvalds@linux-foundation.org \
/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.