Bug 215904
Summary: | kernel BUG at fs/f2fs/inode.c:825! | ||
---|---|---|---|
Product: | File System | Reporter: | bughunter (yanming) |
Component: | f2fs | Assignee: | Default virtual assignee for f2fs (filesystem_f2fs) |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | chao |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.17 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | case.c |
Description
bughunter
2022-04-27 14:27:27 UTC
Could you please try below patch? I doubt the root cause is the same as bug 215895. https://lore.kernel.org/linux-f2fs-devel/20220428024940.12102-1-chao@kernel.org/T/#u Yes, you're right! This bug is caused by the same reason as the previous one. (In reply to bughunter from comment #2) > Yes, you're right! This bug is caused by the same reason as the previous one. Sorry, after adding umount command in your testcase, I can reproduce this issue, and I figure out below patch... https://lore.kernel.org/linux-f2fs-devel/20220430131924.10218-1-chao@kernel.org/T/#u I also forgot to umount the image... Finally, this bug disappears :) Thank you very much! |