From: Matthew Wilcox (Oracle) Date: Tue, 26 May 2026 19:08:02 +0000 (+0100) Subject: ext4: remove mention of PageWriteback X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4e3a55f44b42c2aabd4c1cc3bdb6a01a7107121d;p=thirdparty%2Fkernel%2Flinux.git ext4: remove mention of PageWriteback Update a comment to refer to the concept of writeback instead of the (now obsolete) detail of how it's implemented. Signed-off-by: Matthew Wilcox (Oracle) Reviewed-by: Baokun Li Reviewed-by: Ojaswin Mujoo Reviewed-by: Jan Kara Link: https://patch.msgid.link/20260526190805.341676-1-willy@infradead.org Signed-off-by: Theodore Ts'o --- diff --git a/fs/ext4/page-io.c b/fs/ext4/page-io.c index dc82e7b57e756..bc674aa4a6560 100644 --- a/fs/ext4/page-io.c +++ b/fs/ext4/page-io.c @@ -168,7 +168,7 @@ static void ext4_release_io_end(ext4_io_end_t *io_end) * written. On IO failure, check if journal abort is needed. Note that * we are protected from truncate touching same part of extent tree by the * fact that truncate code waits for all DIO to finish (thus exclusion from - * direct IO is achieved) and also waits for PageWriteback bits. Thus we + * direct IO is achieved) and also waits for writeback to complete. Thus we * cannot get to ext4_ext_truncate() before all IOs overlapping that range are * completed (happens from ext4_free_ioend()). */