]> git.itanic.dy.fi Git - linux-stable/commit
iomap: clear the per-folio dirty bits on all writeback failures
authorChristoph Hellwig <hch@lst.de>
Thu, 7 Dec 2023 07:26:57 +0000 (08:26 +0100)
committerSasha Levin <sashal@kernel.org>
Tue, 26 Mar 2024 22:16:26 +0000 (18:16 -0400)
commitfc6391de33ff894f4acb70a803b846ec9eaf82c7
treebb9fff0beb89840da305ddedab565a7ee337dadd
parent9fc557d489f8163c1aabcb89114b8eba960f4097
iomap: clear the per-folio dirty bits on all writeback failures

[ Upstream commit 7ea1d9b4a840c2dd01d1234663d4a8ef256cfe39 ]

write_cache_pages always clear the page dirty bit before calling into the
file systems, and leaves folios with a writeback failure without the
dirty bit after return.  We also clear the per-block writeback bits for
writeback failures unless no I/O has submitted, which will leave the
folio in an inconsistent state where it doesn't have the folio dirty,
but one or more per-block dirty bits.  This seems to be due the place
where the iomap_clear_range_dirty call was inserted into the existing
not very clearly structured code when adding per-block dirty bit support
and not actually intentional.  Switch to always clearing the dirty on
writeback failure.

Fixes: 4ce02c679722 ("iomap: Add per-block dirty state tracking to improve performance")
Signed-off-by: Christoph Hellwig <hch@lst.de>
Link: https://lore.kernel.org/r/20231207072710.176093-2-hch@lst.de
Signed-off-by: Christian Brauner <brauner@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/iomap/buffered-io.c