From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
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 v5.4
Date: Mon, 16 Sep 2019 06:50:40 -0400 [thread overview]
Message-ID: <f3b4a58a47b4eb3346581f541348a1fc18aabdce.camel@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/filelock-v5.4-1
for you to fetch changes up to cfddf9f4c9f038c91c6c61d5cf3a161731b5c418:
locks: fix a memory leak bug in __break_lease() (2019-08-20 05:48:52 -0400)
----------------------------------------------------------------
Hi Linus,
Just a couple of minor bugfixes, a revision to a tracepoint to account
for some earlier changes to the internals, and a patch to add a pr_warn
message when someone tries to mount a filesystem with '-o mand' on a
kernel that has that support disabled.
----------------------------------------------------------------
Jeff Layton (2):
locks: revise generic_add_lease tracepoint
locks: print a warning when mount fails due to lack of "mand" support
Pavel Begunkov (1):
locks: Fix procfs output for file leases
Wenwen Wang (1):
locks: fix a memory leak bug in __break_lease()
Documentation/filesystems/mandatory-locking.txt | 10 ++++++++++
fs/locks.c | 11 ++++++-----
fs/namespace.c | 11 ++++++++---
include/trace/events/filelock.h | 14 +++++++-------
4 files changed, 31 insertions(+), 15 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
next reply other threads:[~2019-09-16 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 10:50 Jeff Layton [this message]
2019-09-18 20:45 ` 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=f3b4a58a47b4eb3346581f541348a1fc18aabdce.camel@kernel.org \
--to=jlayton@kernel.org \
--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®