https://bugzilla.kernel.org/show_bug.cgi?id=216050
Bug ID: 216050
Summary: fsfs_gc occupies 100% cpu
Product: File System
Version: 2.5
Kernel Version: 5.18
Hardware: All
OS: Linux
Tree: Mainline
St
https://bugzilla.kernel.org/show_bug.cgi?id=216050
--- Comment #1 from Guido (guido.iod...@gmail.com) ---
I was too optimistic. The problem reoccurred.
217 root 20 0 0.0m 99.3 0.0 12:28.48 R f2fs_gc-259:3
the only related error I see the logs is:
30/05/22 13:13 kernel nvme nvme0: missing or inv
On 2022/5/30 9:02, Jack Qiu wrote:
On 2022/5/29 14:58, Chao Yu wrote:
On 2022/5/28 17:35, Jack Qiu via Linux-f2fs-devel wrote:
When find_lock_page return error, page in [i, page_len) will leak.
I doubt it is impossible to fail in find_lock_page due to one extra
reference count was added in pr
https://bugzilla.kernel.org/show_bug.cgi?id=216050
--- Comment #2 from Guido (guido.iod...@gmail.com) ---
my f2fs mounts:
/dev/nvme0n1p3 on / type f2fs
(rw,noatime,lazytime,background_gc=on,nodiscard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adapt
https://bugzilla.kernel.org/show_bug.cgi?id=216050
Guido (guido.iod...@gmail.com) changed:
What|Removed |Added
CC||guido.iod...@gmail.com
Current error handling is at risk of page leaks. However, we dot't seek
any failure scenarios, just use f2fs_bug_on.
Signed-off-by: Jack Qiu
---
fs/f2fs/file.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 100637b1adb3..edb03945
