From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org,
linux-kernel@vger.kernel.org, Neil Brown <neilb@suse.de>
Subject: Re: more nfsd changes for 2.6.26
Date: Fri, 25 Apr 2008 13:57:13 -0400 [thread overview]
Message-ID: <20080425175713.GA1057@fieldses.org> (raw)
In-Reply-To: <20080423213337.GG8302@fieldses.org>
A few more nfsd-related changes are available in the git repository at:
git://linux-nfs.org/~bfields/linux.git for-linus
Mainly this adds a couple new interfaces from Wendy Cheng which allow
userland to tell the nfs server to drop locks held on a given filesystem
(or held by clients accessing the server via a given server ip address),
helpful in high-availability setups when taking down a server whose job
is being taken over by another.
(This could have probably gone with the first pull request, but the
patches were still getting a little work--a small bugfix, and some
fiddling with function names and such.)
The rest are miscellaneous minor bugfixes and cleanup.
--b.
David M. Richter (4):
leases: fix a return-value mixup
leases: when unlocking, skip locking-related steps
leases: move lock allocation earlier in generic_setlease()
leases: remove unneeded variable from fcntl_setlease().
J. Bruce Fields (2):
locks: don't call ->copy_lock methods on return of conflicting locks
nfsd: don't allow setting ctime over v4
James Lentini (1):
Update to NFS/RDMA documentation
Wendy Cheng (2):
lockd: unlock lockd locks associated with a given server ip
lockd: unlock lockd locks held for a certain filesystem
Documentation/filesystems/nfs-rdma.txt | 14 ++++--
fs/lockd/svclock.c | 2 +-
fs/lockd/svcsubs.c | 69 ++++++++++++++++++++++++++++----
fs/locks.c | 32 ++++++++-------
fs/nfsd/nfs4state.c | 3 -
fs/nfsd/nfs4xdr.c | 14 ------
fs/nfsd/nfsctl.c | 65 ++++++++++++++++++++++++++++++
include/linux/fs.h | 1 +
include/linux/lockd/lockd.h | 8 +++-
include/linux/nfsd/nfsd.h | 2 +-
10 files changed, 162 insertions(+), 48 deletions(-)
prev parent reply other threads:[~2008-04-25 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 21:33 J. Bruce Fields
2008-04-25 17:57 ` 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=20080425175713.GA1057@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfsv4@linux-nfs.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome