From: Jeff Layton <jeff.layton@primarydata.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
"J. Bruce Fields" <bfields@fieldses.org>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: [GIT PULL] please pull file locking related changes for v4.5
Date: Mon, 11 Jan 2016 06:49:52 -0500 [thread overview]
Message-ID: <20160111064952.6ee599dd@tlielax.poochiereds.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1969 bytes --]
The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
are available in the git repository at:
git://git.samba.org/jlayton/linux tags/locks-v4.5-1
for you to fetch changes up to b4d629a39e104a8326d5b281ce07c21240c130c9:
locks: rename __posix_lock_file to posix_lock_inode (2016-01-08 11:38:30 -0500)
----------------------------------------------------------------
File locking related changes for v4.5 (pile #1)
Highlights:
- new Kconfig option to allow disabling mandatory locking (which is racy
anyway)
- new tracepoints for setlk and close codepaths
- fix for a long-standing bug in code that handles races between setting
a POSIX lock and close().
----------------------------------------------------------------
Eric W. Biederman (1):
locks: Don't allow mounts in user namespaces to enable mandatory locking
Geliang Tang (1):
locks: use list_first_entry_or_null()
Jeff Layton (7):
locks: Allow disabling mandatory locking at compile time
locks: fix unlock when fcntl_setlk races with a close
locks: don't check for race with close when setting OFD lock
locks: sprinkle some tracepoints around the file locking code
locks: pass inode pointer to locks_free_lock_context
locks: prink more detail when there are leaked locks
locks: rename __posix_lock_file to posix_lock_inode
Paul Gortmaker (1):
fs: make locks.c explicitly non-modular
fs/Kconfig | 10 +++
fs/inode.c | 2 +-
fs/locks.c | 138 ++++++++++++++++++++++++++--------------
fs/namespace.c | 10 +++
include/linux/fs.h | 78 ++++++++++++-----------
include/trace/events/filelock.h | 77 ++++++++++++++++++++++
6 files changed, 232 insertions(+), 83 deletions(-)
--
Jeff Layton <jeff.layton@primarydata.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2016-01-11 11:50 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=20160111064952.6ee599dd@tlielax.poochiereds.net \
--to=jeff.layton@primarydata.com \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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®