From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Neil Brown <neilb@suse.com>, Bruce Fields <bfields@fieldses.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] File locking bugfix for v4.21
Date: Thu, 03 Jan 2019 09:08:54 -0500 [thread overview]
Message-ID: <ce790e2af03fadddc6ede9de94a59c72d13cf591.camel@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
Hi Linus,
The following changes since commit 8e143b90e4d45cca3dc53760d3cfab988bc74571:
Merge tag 'iommu-updates-v4.21' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu (2019-01-01 15:55:29 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/locks-v4.21-2
for you to fetch changes up to bf77ae4c98d721a9aae3840970d46669a78e034a:
locks: fix error in locks_move_blocks() (2019-01-02 20:14:50 -0500)
----------------------------------------------------------------
This is a one-line fix for a bug that syzbot turned up in the new
patches to mitigate the thundering herd when a lock is released.
----------------------------------------------------------------
NeilBrown (1):
locks: fix error in locks_move_blocks()
fs/locks.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Jeff Layton <jlayton@kernel.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
next reply other threads:[~2019-01-03 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 14:08 Jeff Layton [this message]
2019-01-04 4:20 ` [GIT PULL] File locking bugfix for v4.21 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=ce790e2af03fadddc6ede9de94a59c72d13cf591.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=bfields@fieldses.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).