From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Trond Myklebust <trond@netapp.com>
Subject: [GIT] locks.c updates for 2.6.24
Date: Mon, 15 Oct 2007 18:53:16 -0400 [thread overview]
Message-ID: <20071015225316.GB31990@fieldses.org> (raw)
You can pull the following file-locking changes from:
git://linux-nfs.org/~bfields/linux.git locks
Cleanup, minor bugfixes and some documentation patches. They've been in
-mm for a while.
(By the way, I've also started some very primitive lease and flock
tests, available from:
git://linux-nfs.org/~bfields/lock-tests.git
and I'm mainly depending on those and connectathon locking tests for
now.)
--b.
J. Bruce Fields (7):
locks: reverse order of posix_locks_conflict() arguments
locks: kill redundant local variable
locks: fix flock_lock_file() comment
Documentation: move mandatory locking documentation to filesystems/
locks: add warning about mandatory locking races
Documentation: move locks.txt in filesystems/
nfsd: remove IS_ISMNDLCK macro
Matthias Kaehlcke (1):
fs/locks.c: use list_for_each_entry() instead of list_for_each()
Pavel Emelyanov (9):
Memory shortage can result in inconsistent flocks state
Use list_first_entry in locks_wake_up_blocks
locks: Fix potential OOPS in generic_setlease()
Cleanup macros for distinguishing mandatory locks
GFS2: clean up explicit check for mandatory locks
9PFS: clean up explicit check for mandatory locks
AFS: clean up explicit check for mandatory locks
NFS: clean up explicit check for mandatory locks
Rework /proc/locks via seq_files and seq_list helpers
Documentation/00-INDEX | 6 +-
Documentation/filesystems/00-INDEX | 4 +
Documentation/{ => filesystems}/locks.txt | 10 +-
.../mandatory-locking.txt} | 21 ++-
fs/9p/vfs_file.c | 2 +-
fs/afs/flock.c | 3 +-
fs/gfs2/ops_file.c | 4 +-
fs/locks.c | 192 +++++++++-----------
fs/nfs/file.c | 3 +-
fs/nfsd/nfs4state.c | 2 +-
fs/nfsd/vfs.c | 13 +-
fs/proc/proc_misc.c | 19 +-
fs/read_write.c | 2 +-
include/linux/fs.h | 22 ++-
14 files changed, 157 insertions(+), 146 deletions(-)
rename Documentation/{ => filesystems}/locks.txt (87%)
rename Documentation/{mandatory.txt => filesystems/mandatory-locking.txt} (89%)
reply other threads:[~2007-10-15 22:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20071015225316.GB31990@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trond@netapp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®