From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] gfs2 fixes for v5.13-rc5
Date: Mon, 31 May 2021 12:56:06 +0200 [thread overview]
Message-ID: <20210531105606.228314-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following gfs2 fixes for v5.13-rc5.
(I'll follow up with another set of fixes that may require additional
discussion later today.)
Thanks,
Andreas
The following changes since commit d07f6ca923ea0927a1024dfccafc5b53b61cfecc:
Linux 5.13-rc2 (2021-05-16 15:27:44 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v5.13-rc2-fixes
for you to fetch changes up to 1ab19c5de4c537ec0d9b21020395a5b5a6c059b2:
gfs2: Fix use-after-free in gfs2_glock_shrink_scan (2021-05-31 12:03:28 +0200)
----------------------------------------------------------------
Various gfs2 fixes
----------------------------------------------------------------
Andreas Gruenbacher (2):
gfs2: Prevent direct-I/O write fallback errors from getting lost
gfs2: Fix mmap locking for write faults
Bob Peterson (4):
gfs2: Fix I_NEW check in gfs2_dinode_in
gfs2: fix scheduling while atomic bug in glocks
gfs2: fix a deadlock on withdraw-during-mount
gfs2: Clean up revokes on normal withdraws
Hillf Danton (1):
gfs2: Fix use-after-free in gfs2_glock_shrink_scan
fs/gfs2/file.c | 9 +++++++--
fs/gfs2/glock.c | 28 ++++++++++++++++++++++++----
fs/gfs2/glops.c | 2 +-
fs/gfs2/log.c | 6 +++---
fs/gfs2/log.h | 1 +
fs/gfs2/lops.c | 7 ++++++-
fs/gfs2/lops.h | 1 +
fs/gfs2/util.c | 1 +
8 files changed, 44 insertions(+), 11 deletions(-)
next reply other threads:[~2021-05-31 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 10:56 Andreas Gruenbacher [this message]
2021-05-31 16:30 ` [GIT PULL] gfs2 fixes for v5.13-rc5 Linus Torvalds
2021-05-31 20:32 ` Andreas Gruenbacher
2021-05-31 16:36 ` 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=20210531105606.228314-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).