From: Jeff Layton <jlayton@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "<linux-fsdevel@vger.kernel.org>" <linux-fsdevel@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
ira.weiny@intel.com, Bruce Fields <bfields@fieldses.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: [GIT PULL] file lease fix and tracepoint for v5.3
Date: Mon, 08 Jul 2019 08:43:10 -0400 [thread overview]
Message-ID: <fc29b04c3efadbde6ac0352a124a6f436cdf5146.camel@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
The following changes since commit 9e0babf2c06c73cda2c0cd37a1653d823adb40ec:
Linux 5.2-rc5 (2019-06-16 08:49:45 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/locks-v5.3-1
for you to fetch changes up to 387e3746d01c34457d6a73688acd90428725070b:
locks: eliminate false positive conflicts for write lease (2019-06-19 08:49:38 -0400)
----------------------------------------------------------------
Just a couple of small lease-related patches this cycle. One from Ira
to add a new tracepoint that fires during lease conflict checks, and
another patch from Amir to reduce false positives when checking for
lease conflicts.
----------------------------------------------------------------
Amir Goldstein (1):
locks: eliminate false positive conflicts for write lease
Ira Weiny (1):
locks: Add trace_leases_conflict
fs/locks.c | 62 ++++++++++++++++++++++++++++++++++++++++++--------------------
include/linux/fs.h | 4 ++--
include/trace/events/filelock.h | 35 +++++++++++++++++++++++++++++++++++
3 files changed, 79 insertions(+), 22 deletions(-)
--
Jeff Layton <jlayton@redhat.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
next reply other threads:[~2019-07-08 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 12:43 Jeff Layton [this message]
2019-07-11 4:40 ` [GIT PULL] file lease fix and tracepoint for v5.3 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=fc29b04c3efadbde6ac0352a124a6f436cdf5146.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=amir73il@gmail.com \
--cc=bfields@fieldses.org \
--cc=ira.weiny@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).