From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tian Tao <tiantao6@hisilicon.com>,
Luo Longjun <luolongjun@huawei.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Bruce Fields <bfields@fieldses.org>
Subject: [GIT PULL] file locking fixes for v5.13
Date: Mon, 26 Apr 2021 07:18:48 -0400 [thread overview]
Message-ID: <2623d52cefb71fab85fbfbd0315ac48ac89e00ee.camel@kernel.org> (raw)
The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:
Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/locks-v5.13
for you to fetch changes up to cbe6fc4e01421c890d74422cdd04c6b1c8f62dda:
fs/locks: remove useless assignment in fcntl_getlk (2021-04-13 07:26:38 -0400)
----------------------------------------------------------------
When we reworked the blocked locks into a tree structure instead of a
flat list a few releases ago, we lost the ability to see all of the file
locks in /proc/locks. Luo's patch fixes it to dump out all of the
blocked locks instead, which restores the full output.
This changes the format of /proc/locks as the blocked locks are shown at
multiple levels of indentation now, but lslocks (the only common program
I've ID'ed that scrapes this info) seems to be OK with that.
Tian also contributed a small patch to remove a useless assignment.
----------------------------------------------------------------
Luo Longjun (1):
fs/locks: print full locks information
Tian Tao (1):
fs/locks: remove useless assignment in fcntl_getlk
fs/locks.c | 66 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------
1 file changed, 56 insertions(+), 10 deletions(-)
Thanks!
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2021-04-26 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 11:18 Jeff Layton [this message]
2021-04-26 20:57 ` [GIT PULL] file locking fixes for v5.13 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=2623d52cefb71fab85fbfbd0315ac48ac89e00ee.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luolongjun@huawei.com \
--cc=tiantao6@hisilicon.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;
as well as URLs for NNTP newsgroup(s).