linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: NeilBrown <neilb@suse.com>, "asn@redhat.com" <asn@redhat.com>,
	"bfields@vger.kernel.org" <bfields@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] file locking bugfix for v5.1
Date: Tue, 26 Mar 2019 06:56:55 -0400	[thread overview]
Message-ID: <73ec5fc30bc902ba836eb9dabc8bf92023aa427c.camel@kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 843 bytes --]

The following changes since commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00:

  Linux 5.1-rc2 (2019-03-24 14:02:26 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/locks-v5.1

for you to fetch changes up to 945ab8f6de94430c23a82f3cf2e3f6d6f2945ff7:

  locks: wake any locks blocked on request before deadlock check (2019-03-25 08:36:24 -0400)

----------------------------------------------------------------
Hi Linus,

Just a single fix for a bug that crept into POSIX lock deadlock
detection in v5.0.
----------------------------------------------------------------
Jeff Layton (1):
      locks: wake any locks blocked on request before deadlock check

 fs/locks.c | 5 +++++
 1 file changed, 5 insertions(+)
-- 
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-03-26 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26 10:56 Jeff Layton [this message]
2019-03-26 17:45 ` [GIT PULL] file locking bugfix for v5.1 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=73ec5fc30bc902ba836eb9dabc8bf92023aa427c.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=asn@redhat.com \
    --cc=bfields@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.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).