From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: zhanxusheng@xiaomi.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, yangguikun19@qq.com,
jaegeuk@kernel.org, stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't BUG_ON a missing orphan inode at mount
Date: Tue, 17 Nov 2026 16:50:11 +0000 [thread overview]
Message-ID: <179493421127.698822.8936869244996483473.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261105034419.2701443-1-zhanxusheng1024@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 5 Nov 2026 11:44:19 +0800 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: don't BUG_ON a missing orphan inode at mount
https://git.kernel.org/jaegeuk/f2fs/c/b61a029304bb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, yangguikun19@qq.com,
stable@kernel.org, zhanxusheng@xiaomi.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't BUG_ON a missing orphan inode at mount
Date: Tue, 17 Nov 2026 16:50:11 +0000 [thread overview]
Message-ID: <179493421127.698822.8936869244996483473.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261105034419.2701443-1-zhanxusheng1024@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 5 Nov 2026 11:44:19 +0800 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: don't BUG_ON a missing orphan inode at mount
https://git.kernel.org/jaegeuk/f2fs/c/b61a029304bb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-11-17 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 8:00 [f2fs-dev] 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 via Linux-f2fs-devel
2026-11-03 8:00 ` Guikun Yang
2026-11-05 3:44 ` [f2fs-dev] [PATCH] f2fs: don't BUG_ON a missing orphan inode at mount Zhan Xusheng
2026-11-05 3:44 ` Zhan Xusheng
2026-11-11 8:30 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-11-11 8:30 ` Chao Yu
2026-11-17 16:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-11-17 16:50 ` [f2fs-dev] " patchwork-bot+f2fs
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=179493421127.698822.8936869244996483473.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=stable@kernel.org \
--cc=yangguikun19@qq.com \
--cc=zhanxusheng1024@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.