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.16-rc2
Date: Thu, 18 Nov 2021 00:36:56 +0100 [thread overview]
Message-ID: <20211117233656.77861-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following gfs2 fixes for -rc2. The one thing that
stands out is this commit:
gfs2: Prevent endless loops in gfs2_file_buffered_write
We have a choice here between the proper fix in iomap_write_iter and
generic_perform_write and this patch, which is just a workaround. I've tried
to get your feedback on this before:
https://lore.kernel.org/all/20211110174457.533866-1-agruenba@redhat.com/
To me, it seems to be too late for the proper fix for v5.16 now; please advise
if you think otherwise.
Thanks,
Andreas
The following changes since commit 78805cbe5d72ad27a56962a8072edbcb45ca1180:
Merge tag 'gfs2-v5.15-rc5-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2021-11-02 12:35:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v5.16-rc2-fixes
for you to fetch changes up to 554c577cee95bdc1d03d9f457e57dc96eb791845:
gfs2: Prevent endless loops in gfs2_file_buffered_write (2021-11-10 18:22:37 +0100)
----------------------------------------------------------------
Fixes in gfs2:
* The current iomap_file_buffered_write behavior of failing the entire
write when part of the user buffer cannot be faulted in leads to an
endless loop in gfs2. Work around that in gfs2 for now.
* Various other bugs all over the place.
----------------------------------------------------------------
Andreas Gruenbacher (5):
gfs2: Only dereference i->iov when iter_is_iovec(i)
gfs2: Fix atomic bug in gfs2_instantiate
gfs2: Fix length of holes reported at end-of-file
gfs2: Fix "Introduce flag for glock holder auto-demotion"
gfs2: Prevent endless loops in gfs2_file_buffered_write
Bob Peterson (1):
gfs2: release iopen glock early in evict
fs/gfs2/bmap.c | 2 +-
fs/gfs2/file.c | 9 ++++++---
fs/gfs2/glock.c | 12 ++++--------
fs/gfs2/super.c | 14 +++++++-------
4 files changed, 18 insertions(+), 19 deletions(-)
next reply other threads:[~2021-11-17 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 23:36 Andreas Gruenbacher [this message]
2021-11-17 23:55 ` Linus Torvalds
2021-11-17 23:58 ` 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=20211117233656.77861-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
all inboxes | Powered by JetHome®