From: Brian Foster <bfoster@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/3] misc iomap/xfs writeback fixes
Date: Thu, 29 Oct 2020 09:23:22 -0400 [thread overview]
Message-ID: <20201029132325.1663790-1-bfoster@redhat.com> (raw)
Hi all,
Patch 1 is actually a repost of the original fix I posted[1] for the
truncate down zeroing issue. Patch 2 has some minor tweaks based on
feedback on v1 from Christoph. Patch 3 is new and fixes up some of the
remaining broken iomap writepage error handling logic (also discussed in
the v1 thread). Thoughts, reviews, flames appreciated.
Brian
v2:
- Repost original XFS truncate down post-EOF zeroing fix.
- Pass file offset to iomap ->discard_page() callback.
- Add patch 3 to fix up iomap writepage error handling.
v1: https://lore.kernel.org/linux-xfs/20201026182019.1547662-1-bfoster@redhat.com/
[1] https://lore.kernel.org/linux-xfs/20201007143509.669729-1-bfoster@redhat.com/
Brian Foster (3):
xfs: flush new eof page on truncate to avoid post-eof corruption
iomap: support partial page discard on writeback block mapping failure
iomap: clean up writeback state logic on writepage error
fs/iomap/buffered-io.c | 30 ++++++++++--------------------
fs/xfs/xfs_aops.c | 13 +++++++------
fs/xfs/xfs_iops.c | 10 ++++++++++
include/linux/iomap.h | 2 +-
4 files changed, 28 insertions(+), 27 deletions(-)
--
2.25.4
next reply other threads:[~2020-10-29 13:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 13:23 Brian Foster [this message]
2020-10-29 13:23 ` [PATCH v2 1/3] xfs: flush new eof page on truncate to avoid post-eof corruption Brian Foster
2020-10-29 15:04 ` Christoph Hellwig
2020-10-29 21:44 ` Darrick J. Wong
2020-10-30 23:23 ` Allison Henderson
2020-10-29 13:23 ` [PATCH v2 2/3] iomap: support partial page discard on writeback block mapping failure Brian Foster
2020-10-29 15:06 ` Christoph Hellwig
2020-10-29 15:27 ` Darrick J. Wong
2020-10-29 16:07 ` Brian Foster
2020-10-29 16:12 ` Darrick J. Wong
2020-10-29 16:33 ` [PATCH v2.1 " Brian Foster
2020-10-29 21:45 ` Darrick J. Wong
2020-10-30 23:23 ` Allison Henderson
2020-10-29 13:23 ` [PATCH v2 3/3] iomap: clean up writeback state logic on writepage error Brian Foster
2020-10-29 15:11 ` Christoph Hellwig
2020-10-29 21:48 ` Darrick J. Wong
2020-10-30 23:23 ` Allison Henderson
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=20201029132325.1663790-1-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.