From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/7] gfs2 fixes
Date: Fri, 13 May 2022 22:48:03 +0200 [thread overview]
Message-ID: <20220513204810.4123139-1-agruenba@redhat.com> (raw)
Hello,
here's a bunch of fixes and related cleanups for the filesystem
corruption we've sometimes seen since commit 00bfe02f4796 ("gfs2: Fix
mmap + page fault deadlocks for buffered I/O").
Thanks,
Andreas
Andreas Gruenbacher (7):
gfs2: Fix filesystem block deallocation for short writes
gfs2: Variable rename
gfs2: Clean up use of fault_in_iov_iter_{read,write}able
gfs2: Pull return value test out of should_fault_in_pages
gfs2: Align read and write chunks to the page cache
gfs2: buffered write prefaulting
gfs2: Stop using glock holder auto-demotion for now
fs/gfs2/bmap.c | 11 ++--
fs/gfs2/file.c | 139 ++++++++++++++++++++++---------------------------
2 files changed, 68 insertions(+), 82 deletions(-)
--
2.35.1
next reply other threads:[~2022-05-13 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 20:48 Andreas Gruenbacher [this message]
2022-05-13 20:48 ` [Cluster-devel] [PATCH 1/7] gfs2: Fix filesystem block deallocation for short writes Andreas Gruenbacher
2022-05-13 20:48 ` [Cluster-devel] [PATCH 2/7] gfs2: Variable rename Andreas Gruenbacher
2022-05-13 20:48 ` [Cluster-devel] [PATCH 3/7] gfs2: Clean up use of fault_in_iov_iter_{read, write}able Andreas Gruenbacher
2022-05-13 20:48 ` [Cluster-devel] [PATCH 4/7] gfs2: Pull return value test out of should_fault_in_pages Andreas Gruenbacher
2022-05-13 20:48 ` [Cluster-devel] [PATCH 5/7] gfs2: Align read and write chunks to the page cache Andreas Gruenbacher
2022-05-13 20:48 ` [Cluster-devel] [PATCH 6/7] gfs2: buffered write prefaulting Andreas Gruenbacher
2022-05-13 20:48 ` [Cluster-devel] [PATCH 7/7] gfs2: Stop using glock holder auto-demotion for now Andreas Gruenbacher
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=20220513204810.4123139-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
/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).