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: Recognize mmap + page fault self-recursion to prevent deadlocks
Date: Wed, 2 Jun 2021 13:26:09 +0200 [thread overview]
Message-ID: <20210602112609.355793-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following fixes for partially addressing the mmap +
page fault deadlocks. It's not clear to me if and when we'll find a better
solution, and those fixes prevent a kernel BUG in the simple self-recursion
case at least. (This is the case that the new fstest [*] reproduces.)
[*] https://lore.kernel.org/fstests/20210531152604.240462-1-agruenba@redhat.com/
Thanks,
Andreas
The following changes since commit d5b8145455c629e7f157d2da46a9b2fba483f235:
Revert "gfs2: Fix mmap locking for write faults" (2021-06-01 23:16:42 +0200)
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-fixes3
for you to fetch changes up to 485805ef8389eb1caa484cbb66e815afac00879d:
gfs2: Fix mmap + page fault deadlocks (part 1) (2021-06-02 11:44:54 +0200)
----------------------------------------------------------------
gfs2: Recognize mmap + page fault self-recursion to prevent deadlocks
----------------------------------------------------------------
Andreas Gruenbacher (4):
gfs2: Clean up the error handling in gfs2_page_mkwrite
gfs2: Add wrapper for iomap_file_buffered_write
gfs2: Add gfs2_holder_is_compatible helper
gfs2: Fix mmap + page fault deadlocks (part 1)
fs/gfs2/file.c | 117 +++++++++++++++++++++++++++++++++++++++-----------------
fs/gfs2/glock.h | 14 +++++++
2 files changed, 95 insertions(+), 36 deletions(-)
reply other threads:[~2021-06-02 11:27 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=20210602112609.355793-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).