From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Konstantin Khorenko <khorenko@virtuozzo.com>,
Bruce Fields <bfields@fieldses.org>
Subject: [GIT PULL] file locking updates for 4.19
Date: Mon, 13 Aug 2018 07:00:23 -0400 [thread overview]
Message-ID: <a7bddd53bf70f7aeb2c761ab84411bd2a285d7af.camel@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
The following changes since commit 2837461dbe6f4a9acc0d86f88825888109211c99:
Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2018-06-14 16:35:32 +0900)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/locks-v4.19-1
for you to fetch changes up to da33a871ba178dbe81da7d755818d3c2088cae32:
locks: remove misleading obsolete comment (2018-08-08 12:59:06 -0400)
----------------------------------------------------------------
Just a couple of patches from Konstantin to fix /proc/locks when the
process that set the lock has exited, and a new tracepoint for the
flock() codepath. Also threw in mailmap entries for my addresses and a
comment cleanup.
----------------------------------------------------------------
Jeff Layton (3):
locks: add tracepoint in flock codepath
mailmap: remap some of my email addresses to kernel.org address
locks: remove misleading obsolete comment
Konstantin Khorenko (2):
fs/lock: skip lock owner pid translation in case we are in init_pid_ns
fs/lock: show locks taken by processes from another pidns
.mailmap | 3 +++
fs/locks.c | 20 +++++++++++---------
include/trace/events/filelock.h | 5 ++++-
3 files changed, 18 insertions(+), 10 deletions(-)
--
Jeff Layton <jlayton@kernel.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
reply other threads:[~2018-08-13 11:00 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=a7bddd53bf70f7aeb2c761ab84411bd2a285d7af.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=bfields@fieldses.org \
--cc=khorenko@virtuozzo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome