[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240829085407.3331490-2-zhangshida@kylinos.cn>
Date: Thu, 29 Aug 2024 16:54:05 +0800
From: zhangshida <starzhangzsd@...il.com>
To: tytso@....edu,
adilger.kernel@...ger.ca,
jack@...e.com,
ebiggers@...nel.org
Cc: linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org,
zhangshida@...inos.cn,
starzhangzsd@...il.com,
Jan Kara <jack@...e.cz>
Subject: [PATCH 1/3] ext4: persist the new uptodate buffers in ext4_journalled_zero_new_buffers
From: Shida Zhang <zhangshida@...inos.cn>
For new uptodate buffers we also need to call write_end_fn() to persist the
uptodate content, similarly as folio_zero_new_buffers() does it.
Suggested-by: Jan Kara <jack@...e.cz>
Signed-off-by: Shida Zhang <zhangshida@...inos.cn>
---
fs/ext4/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index 941c1c0d5c6e..a0a55cb8db53 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -1389,9 +1389,9 @@ static void ext4_journalled_zero_new_buffers(handle_t *handle,
size = min(to, block_end) - start;
folio_zero_range(folio, start, size);
- write_end_fn(handle, inode, bh);
}
clear_buffer_new(bh);
+ write_end_fn(handle, inode, bh);
}
}
block_start = block_end;
--
2.33.0
Powered by blists - more mailing lists