summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2026-08-03 18:00:38 +0200
committerTheodore Ts'o <tytso@mit.edu>2026-08-06 10:24:31 -0400
commit5aa98f874c013bcce9bb84ffded2f0ef886e4e33 (patch)
treeb32fd34e5414f79a29c8a8ef708c8cc299c33e28
parent54b6bd40898de7906acb2bccc9a96d1b8e6b4323 (diff)
downloadlinux-stable-5aa98f874c013bcce9bb84ffded2f0ef886e4e33.tar.gz
linux-stable-5aa98f874c013bcce9bb84ffded2f0ef886e4e33.zip
ext4: fix spurious message about orphan cleanup on RO fs
When orphan_file feature is enabled, ext4_orphan_cleanup() was always walking through the orphan file looking for orphan inodes. This is mostly harmless but for read-only filesystem it results in spurious "orphan cleanup on readonly fs" message and in other cornercases it could result in similar somewhat misleading messages. Skip orphan cleanup if the orphan file is empty to avoid confusing messages. Fixes: 02f310fcf47f ("ext4: Speedup ext4 orphan inode handling") Reported-by: Tigran Aivazian <aivazian.tigran@gmail.com> Signed-off-by: Jan Kara <jack@suse.cz> Reviewed-by: Baokun Li <libaokun@linux.alibaba.com> Link: https://patch.msgid.link/20260803160037.64285-2-jack@suse.cz Signed-off-by: Theodore Ts'o <tytso@mit.edu>
-rw-r--r--fs/ext4/orphan.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/ext4/orphan.c b/fs/ext4/orphan.c
index 646c3077b6d2..b4675aa7ea96 100644
--- a/fs/ext4/orphan.c
+++ b/fs/ext4/orphan.c
@@ -389,7 +389,7 @@ void ext4_orphan_cleanup(struct super_block *sb, struct ext4_super_block *es)
struct ext4_orphan_info *oi = &EXT4_SB(sb)->s_orphan_info;
int inodes_per_ob = ext4_inodes_per_orphan_block(sb);
- if (!es->s_last_orphan && !oi->of_blocks) {
+ if (!es->s_last_orphan && ext4_orphan_file_empty(sb)) {
ext4_debug("no orphan inodes to clean up\n");
return;
}