From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nikolay Borisov <nborisov@suse.com>, Neil Brown <neilb@suse.com>,
Bruce Fields <bfields@fieldses.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] File locking changes for v4.21
Date: Mon, 24 Dec 2018 06:06:16 -0500 [thread overview]
Message-ID: <9d429d110c16472f531e9dcd0a2ac6dfcdc0ad20.camel@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]
The following changes since commit
ccda4af0f4b92f7b4c308d3acc262f4a7e3affad:
Linux 4.20-rc2 (2018-11-11 17:12:31 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/locks-v4.21-1
for you to fetch changes up to 052b8cfa4070caa53125cd589da0cfe744132a94:
locks: Use inode_is_open_for_write (2018-12-17 07:19:46 -0500)
----------------------------------------------------------------
The main change in this set is Neil Brown's work to reduce the
thundering herd problem when a heavily-contended file lock is released.
Previously we'd always wake up all waiters when this occurred. With this
set, we'll now we only wake up waiters that were blocked on the range
being released.
----------------------------------------------------------------
NeilBrown (12):
fs/locks: rename some lists and pointers.
fs/locks: split out __locks_wake_up_blocks().
NFS: use locks_copy_lock() to copy locks.
gfs2: properly initial file_lock used for unlock.
ocfs2: properly initial file_lock used for unlock.
fs/locks: use properly initialized file_lock when unlocking.
fs/locks: allow a lock request to block other requests.
fs/locks: always delete_block after waiting.
fs/locks: change all *_conflict() functions to return bool.
fs/locks: create a tree of dependent requests.
fs/locks: merge posix_unblock_lock() and locks_delete_block()
fs/locks: remove unnecessary white space.
Nikolay Borisov (1):
locks: Use inode_is_open_for_write
fs/cifs/file.c | 4 +-
fs/gfs2/file.c | 10 +-
fs/lockd/svclock.c | 2 +-
fs/locks.c | 344 +++++++++++++++++++++++++---------------
fs/nfs/nfs4proc.c | 6 +-
fs/nfsd/nfs4state.c | 6 +-
fs/ocfs2/locks.c | 10 +-
include/linux/fs.h | 13 +-
include/trace/events/filelock.h | 16 +-
9 files changed, 253 insertions(+), 158 deletions(-)
--
Jeff Layton <jlayton@kernel.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
next reply other threads:[~2018-12-24 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 11:06 Jeff Layton [this message]
2018-12-28 1:45 ` [GIT PULL] File locking changes for v4.21 pr-tracker-bot
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=9d429d110c16472f531e9dcd0a2ac6dfcdc0ad20.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=neilb@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox