[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250810044806.3433783-2-alexjlzheng@tencent.com>
Date: Sun, 10 Aug 2025 12:48:03 +0800
From: alexjlzheng@...il.com
To: brauner@...nel.org,
djwong@...nel.org
Cc: linux-xfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org,
Jinliang Zheng <alexjlzheng@...cent.com>
Subject: [PATCH 1/4] iomap: make sure iomap_adjust_read_range() are aligned with block_size
From: Jinliang Zheng <alexjlzheng@...cent.com>
iomap_folio_state marks the uptodate state in units of block_size, so
it is better to check that pos and length are aligned with block_size.
Signed-off-by: Jinliang Zheng <alexjlzheng@...cent.com>
---
fs/iomap/buffered-io.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
index fd827398afd2..27fa93ca8675 100644
--- a/fs/iomap/buffered-io.c
+++ b/fs/iomap/buffered-io.c
@@ -234,6 +234,9 @@ static void iomap_adjust_read_range(struct inode *inode, struct folio *folio,
unsigned first = poff >> block_bits;
unsigned last = (poff + plen - 1) >> block_bits;
+ BUG_ON(*pos % block_size);
+ BUG_ON(length % block_size);
+
/*
* If the block size is smaller than the page size, we need to check the
* per-block uptodate status and adjust the offset and length if needed
--
2.49.0
Powered by blists - more mailing lists