summaryrefslogtreecommitdiff
path: root/io_uring/splice.h
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2023-12-07 10:26:57 +0300
committerSasha Levin <sashal@kernel.org>2024-03-27 01:16:26 +0300
commitfc6391de33ff894f4acb70a803b846ec9eaf82c7 (patch)
treebb9fff0beb89840da305ddedab565a7ee337dadd /io_uring/splice.h
parent9fc557d489f8163c1aabcb89114b8eba960f4097 (diff)
downloadlinux-fc6391de33ff894f4acb70a803b846ec9eaf82c7.tar.xz
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>
Diffstat (limited to 'io_uring/splice.h')
0 files changed, 0 insertions, 0 deletions