From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Qi Han <hanqi@vivo.com>, jaegeuk@kernel.org
Cc: 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: Tue, 8 Oct 2024 11:25:45 +0800 [thread overview]
Message-ID: <82e4a8bb-29d4-4ce8-bc04-985b08801aeb@kernel.org> (raw)
In-Reply-To: <20240918084400.1821317-1-hanqi@vivo.com>
On 2024/9/18 16:44, Qi Han 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
>
> The root cause is: creating large files during disable checkpoint
> period results in not enough free segments, so when writing back root
> inode will failed in f2fs_enable_checkpoint. When umount the file
> system after enabling checkpoint, the root inode is dirty in
> f2fs_evict_inode function, which triggers BUG_ON. The steps to
> reproduce are as follows:
>
> dd if=/dev/zero of=f2fs.img bs=1M count=55
> mount f2fs.img f2fs_dir -o checkpoint=disable:10%
> dd if=/dev/zero of=big bs=1M count=50
> sync
> rm big
> mount -o remount,checkpoint=enable f2fs_dir
> umount f2fs_dir
>
> Let's redirty inode when there is not free segments during checkpoint
> is disable.
>
> Signed-off-by: Qi Han <hanqi@vivo.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-10-08 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 8:44 [f2fs-dev] [PATCH] f2fs: fix f2fs_bug_on when uninstalling filesystem call f2fs_evict_inode Qi Han via Linux-f2fs-devel
2024-10-08 3:25 ` Chao Yu via Linux-f2fs-devel [this message]
2024-10-28 17:40 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
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=82e4a8bb-29d4-4ce8-bc04-985b08801aeb@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=hanqi@vivo.com \
--cc=jaegeuk@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).