From: Zhan Xusheng <zhanxusheng1024@gmail.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Guikun Yang <yangguikun19@qq.com>,
zhanxusheng@xiaomi.com, stable@kernel.org
Subject: [PATCH] f2fs: don't BUG_ON a missing orphan inode at mount
Date: Thu, 5 Nov 2026 11:44:19 +0800 [thread overview]
Message-ID: <20261105034419.2701443-1-zhanxusheng1024@gmail.com> (raw)
In-Reply-To: <tencent_B30A444DF94444D1A63A7D6F8E2039F1990A@qq.com>
From: Zhan Xusheng <zhanxusheng@xiaomi.com>
recover_orphan_inode() treats -ENOENT from f2fs_iget() as a kernel
bug, but the ino comes from the on-disk orphan block. An image whose
orphan entry names an inode without a NAT entry hits the BUG_ON at
mount with CONFIG_F2FS_CHECK_FS, or a WARN and a failed mount
without it.
To reproduce, unlink a file while it is still open, sync, crash,
then change ino[0] in the checkpoint's orphan block to an unused
nid and mount:
kernel BUG at fs/f2fs/checkpoint.c:967!
RIP: 0010:f2fs_recover_orphan_inodes+0x6a3/0x9a0
Treat it as corruption, the same way the entry_count check does:
fail the mount with -EFSCORRUPTED and record
ERROR_INCONSISTENT_ORPHAN for fsck.
Fixes: 8c14bfadeac2 ("f2fs: handle error of f2fs_iget correctly")
Reported-by: Guikun Yang <yangguikun19@qq.com>
Closes: https://lore.kernel.org/linux-f2fs-devel/tencent_B30A444DF94444D1A63A7D6F8E2039F1990A@qq.com/
Cc: stable@kernel.org
Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
---
Tested in QEMU on f2fs/dev with CONFIG_F2FS_CHECK_FS=y:
orphan ino before after
4 (real) mounts mounts
1000 BUG at mount -EFSCORRUPTED, s_errors bit set
fs/f2fs/checkpoint.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
index 1ed38c668fc5..e57904a33ff8 100644
--- a/fs/f2fs/checkpoint.c
+++ b/fs/f2fs/checkpoint.c
@@ -960,12 +960,13 @@ static int recover_orphan_inode(struct f2fs_sb_info *sbi, nid_t ino)
inode = f2fs_iget_retry(sbi->sb, ino);
if (IS_ERR(inode)) {
- /*
- * there should be a bug that we can't find the entry
- * to orphan inode.
- */
- f2fs_bug_on(sbi, PTR_ERR(inode) == -ENOENT);
- return PTR_ERR(inode);
+ if (PTR_ERR(inode) != -ENOENT)
+ return PTR_ERR(inode);
+ /* The orphan area lists an inode that does not exist. */
+ f2fs_err(sbi, "orphan inode %u does not exist", ino);
+ set_sbi_flag(sbi, SBI_NEED_FSCK);
+ f2fs_handle_error(sbi, ERROR_INCONSISTENT_ORPHAN);
+ return -EFSCORRUPTED;
}
err = f2fs_dquot_initialize(inode);
base-commit: 9b12299b437e0cc3ebf402e7b36a89cc69151238
--
2.43.0
prev parent reply other threads:[~2026-11-05 3:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 8:00 f2fs: orphan entry pointing at an inode with no NAT entry triggers f2fs_bug_on() in recover_orphan_inode() - kernel BUG at mount with CONFIG_F2FS_CHECK_FS Guikun Yang
2026-11-05 3:44 ` Zhan Xusheng [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261105034419.2701443-1-zhanxusheng1024@gmail.com \
--to=zhanxusheng1024@gmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=yangguikun19@qq.com \
--cc=zhanxusheng@xiaomi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®