From: patchwork-bot+f2fs@kernel.org
To: Qi Han <hanqi@vivo.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix f2fs_bug_on when uninstalling filesystem call f2fs_evict_inode.
Date: Mon, 28 Oct 2024 17:40:36 +0000 [thread overview]
Message-ID: <173013723649.126843.961245482692582747.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240918084400.1821317-1-hanqi@vivo.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 18 Sep 2024 02:44:00 -0600 you wrote:
> creating a large files during checkpoint disable until it runs out of
> space and then delete it, then remount to enable checkpoint again, and
> then unmount the filesystem triggers the f2fs_bug_on as below:
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/inode.c:896!
> CPU: 2 UID: 0 PID: 1286 Comm: umount Not tainted 6.11.0-rc7-dirty #360
> Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
> RIP: 0010:f2fs_evict_inode+0x58c/0x610
> Call Trace:
> __die_body+0x15/0x60
> die+0x33/0x50
> do_trap+0x10a/0x120
> f2fs_evict_inode+0x58c/0x610
> do_error_trap+0x60/0x80
> f2fs_evict_inode+0x58c/0x610
> exc_invalid_op+0x53/0x60
> f2fs_evict_inode+0x58c/0x610
> asm_exc_invalid_op+0x16/0x20
> f2fs_evict_inode+0x58c/0x610
> evict+0x101/0x260
> dispose_list+0x30/0x50
> evict_inodes+0x140/0x190
> generic_shutdown_super+0x2f/0x150
> kill_block_super+0x11/0x40
> kill_f2fs_super+0x7d/0x140
> deactivate_locked_super+0x2a/0x70
> cleanup_mnt+0xb3/0x140
> task_work_run+0x61/0x90
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix f2fs_bug_on when uninstalling filesystem call f2fs_evict_inode.
https://git.kernel.org/jaegeuk/f2fs/c/d5c367ef8287
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-10-28 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 8:44 Qi Han
2024-10-08 3:25 ` Chao Yu
2024-10-28 17:40 ` patchwork-bot+f2fs [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=173013723649.126843.961245482692582747.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=hanqi@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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®