From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <linus971@gmail.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Bruce Fields <bfields@fieldses.org>
Subject: [GIT PULL] /proc/locks formatting fix for v5.5
Date: Sun, 29 Dec 2019 09:27:58 -0500 [thread overview]
Message-ID: <e5d1c0a5e5e92083d8ce0bc1e48194a6d70fb918.camel@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
The following changes since commit 46cf053efec6a3a5f343fead837777efe8252a46:
Linux 5.5-rc3 (2019-12-22 17:02:23 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/locks-v5.5-1
for you to fetch changes up to 98ca480a8f22fdbd768e3dad07024c8d4856576c:
locks: print unsigned ino in /proc/locks (2019-12-29 09:00:58 -0500)
----------------------------------------------------------------
This is a trivial fix for a _very_ long standing bug in /proc/locks
formatting. Ordinarily, I'd wait for the merge window for something like
this, but it is making it difficult to validate some overlayfs fixes.
I've also gone ahead and marked this for stable. My hope is that no one
is actually depending on seeing these values represented as negative
numbers, but if that assumption is too risky we can drop the Cc.
----------------------------------------------------------------
Amir Goldstein (1):
locks: print unsigned ino in /proc/locks
fs/locks.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Jeff Layton <jlayton@poochiereds.net>
--
Jeff Layton <jlayton@kernel.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
reply other threads:[~2019-12-29 14:28 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=e5d1c0a5e5e92083d8ce0bc1e48194a6d70fb918.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=amir73il@gmail.com \
--cc=bfields@fieldses.org \
--cc=linus971@gmail.com \
--cc=linux-fsdevel@vger.kernel.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).