[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2023-07-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 kelak (ale...@gmx.net) changed: What|Removed |Added CC||ale...@gmx.net --- Comment #175

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2023-08-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #176 from Guido (guido.iod...@gmail.com) --- After several months the bug occurred again with kernel 6.5 rc4. After rebooting with REISUB, I tried forcing GC with the usual script and it gave me no problems. -- You may reply to this

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2023-08-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #177 from Chao Yu (c...@kernel.org) --- (In reply to kelak from comment #175) > Still happens on my system with 6.4.x kernels after about 4 days (today the > second time in the last two weeks): Jaegeuk has proposed a workaround soluti

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2023-08-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #178 from kelak (ale...@gmx.net) --- >Jaegeuk has proposed a workaround solution as below, it aims to enable from >6.6-rc1, could you please have a try with it? > >https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2023-08-18 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #179 from Guido (guido.iod...@gmail.com) --- (In reply to kelak from comment #178) > >Jaegeuk has proposed a workaround solution as below, it aims to enable from > >6.6-rc1, could you please have a try with it? > > > > >https://git.ker

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2023-08-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #180 from kelak (ale...@gmx.net) --- (In reply to Guido from comment #179) > (In reply to kelak from comment #178) > > >Jaegeuk has proposed a workaround solution as below, it aims to enable > from > > >6.6-rc1, could you please have a

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2023-08-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #181 from Guido (guido.iod...@gmail.com) --- The fact that dirty segments don't go below 1 suggests that the bug is not completely fixed even with this patch. This is unfortunate because the 5.15 kernel, which is not affected by th

[f2fs-dev] [Bug 210797] resize.f2fs over 2 (LVM) disks corrupts whole filesystem

2023-09-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210797 Tomas Thiemel (thie...@centrum.cz) changed: What|Removed |Added Status|ASSIGNED|RESOLVED Res

[f2fs-dev] [Bug 210795] fsck.f2fs - 1.14.0 - error when not /dev/vgXX/lvYYY path provided - [ASSERT] (init_sb_info:1017) !strcmp((char *)sb->devs[i].path, (char *)c.devices[i].path)

2023-09-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210795 Tomas Thiemel (thie...@centrum.cz) changed: What|Removed |Added Status|ASSIGNED|RESOLVED Res

[f2fs-dev] [Bug 218096] New: first 4K all zeros when release_cblocks set, reserve_cblocks restores access

2023-11-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218096 Bug ID: 218096 Summary: first 4K all zeros when release_cblocks set, reserve_cblocks restores access Product: File System Version: 2.5 Hardware: All OS: Lin

[f2fs-dev] [Bug 218349] New: f2fs partitions corrupted during power failures and cannot be fixed with fsck.

2024-01-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218349 Bug ID: 218349 Summary: f2fs partitions corrupted during power failures and cannot be fixed with fsck. Product: File System Version: 2.5 Hardware: AMD OS: L

[f2fs-dev] [Bug 218349] f2fs partitions corrupted during power failures and cannot be fixed with fsck.

2024-01-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218349 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[f2fs-dev] [Bug 218471] New: F2FS fails to mount rw at boot with "invalid zstd compress level: 6"

2024-02-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218471 Bug ID: 218471 Summary: F2FS fails to mount rw at boot with "invalid zstd compress level: 6" Product: File System Version: 2.5 Hardware: All OS: Linux

[f2fs-dev] [Bug 218471] F2FS fails to mount rw at boot with "invalid zstd compress level: 6"

2024-02-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218471 --- Comment #1 from Dhya Pacifica (d...@picorealm.net) --- The changelog for the Debian linux-image-6.1.0-18-amd64 kernel package lists: - f2fs: clean up i_compress_flag and i_compress_level usage - f2fs: convert to use bitmap API - f

[f2fs-dev] [Bug 218471] F2FS fails to mount rw at boot with "invalid zstd compress level: 6"

2024-02-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218471 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Kernel Version||6.1.76 Regres

[f2fs-dev] [Bug 218471] F2FS fails to mount rw at boot with "invalid zstd compress level: 6"

2024-02-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218471 --- Comment #2 from Salvatore Bonaccorso (car...@debian.org) --- regressions list report: https://lore.kernel.org/regressions/zcu3vcrt9vopu...@eldamar.lan/T/#u Debian downstream bugreport: https://bugs.debian.org/1063422 -- You may reply to thi

[f2fs-dev] [Bug 218471] F2FS fails to mount rw at boot with "invalid zstd compress level: 6"

2024-02-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218471 Jaegeuk Kim (jaeg...@kernel.org) changed: What|Removed |Added CC||jaeg...@kernel.org ---

[f2fs-dev] [Bug 218471] F2FS fails to mount rw at boot with "invalid zstd compress level: 6"

2024-02-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218471 Chao Yu (c...@kernel.org) changed: What|Removed |Added CC||c...@kernel.org --- Comment #

[f2fs-dev] [Bug 218349] f2fs partitions corrupted during power failures and cannot be fixed with fsck.

2024-03-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218349 Kane Ch'in (qinfd2...@lzu.edu.cn) changed: What|Removed |Added Status|ASSIGNED|RESOLVED Reso

[f2fs-dev] [Bug 218349] f2fs partitions corrupted during power failures and cannot be fixed with fsck.

2024-03-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218349 --- Comment #3 from Chao Yu (c...@kernel.org) --- (In reply to Kane Ch'in from comment #2) > That works! Thank you for your efforts. Thank you for the confirmation! I found above link is expired, let me attach the lore one for who wants check it

[f2fs-dev] [Bug 218769] New: fsck seems unable to solve corruption

2024-04-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218769 Bug ID: 218769 Summary: fsck seems unable to solve corruption Product: File System Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: high

[f2fs-dev] [Bug 218770] New: fsck seems unable to solve corruption

2024-04-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 Bug ID: 218770 Summary: fsck seems unable to solve corruption Product: File System Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: high

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-04-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #1 from Guido (guido.iod...@gmail.com) --- Created attachment 306205 --> https://bugzilla.kernel.org/attachment.cgi?id=306205&action=edit fsck -- You may reply to this email to add a comment. You are receiving this mail because: Y

[f2fs-dev] [Bug 218769] fsck seems unable to solve corruption

2024-04-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218769 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Reso

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-04-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #2 from Artem S. Tashkinov (a...@gmx.com) --- *** Bug 218769 has been marked as a duplicate of this bug. *** -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-04-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Reso

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-04-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Resolution|ANSWERED|CODE_FIX Regr

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-04-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #5 from Guido (guido.iod...@gmail.com) --- (In reply to Artem S. Tashkinov from comment #4) > On 4/24/24 12:21 PM, Tor Vic wrote: > > > > I can confirm the constant fsck issue, and it was fixed in my case by > > the following patch:

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-04-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 Jaegeuk Kim (jaeg...@kernel.org) changed: What|Removed |Added CC||jaeg...@kernel.org ---

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-04-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #7 from Guido (guido.iod...@gmail.com) --- (In reply to Jaegeuk Kim from comment #6) > Thank you for the report. It seems I need to reapply that patch indeed. Does rc6 contain the reapplied patch? -- You may reply to this email to a

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-05-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #8 from Guido (guido.iod...@gmail.com) --- The problem persists in the released version of kernel 6.9 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. _

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-05-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #9 from Jaegeuk Kim (jaeg...@kernel.org) --- https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev&id=b864ddb57eb00c4ea1e6801c7b2f70f1db2a7f4b is going to be merged in upcoming weeks and LTS probably will pick

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-05-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #10 from Guido (guido.iod...@gmail.com) --- I applied the patch to 6.9 and it works fine. I am a bit surprised that it is not already applied to 6.9.1. -- You may reply to this email to add a comment. You are receiving this mail bec

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #11 from Jaegeuk Kim (jaeg...@kernel.org) --- The patch is in the next pull request. https://patchwork.kernel.org/project/f2fs/patch/zkumxs7pogimb...@google.com/ Once Linus pulled it, I can ask Greg to queue it in -stable. -- You ma

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #12 from Guido (guido.iod...@gmail.com) --- (In reply to Jaegeuk Kim from comment #11) > The patch is in the next pull request. > https://patchwork.kernel.org/project/f2fs/patch/zkumxs7pogimb...@google.com/ > > Once Linus pulled it, I

[f2fs-dev] [Bug 218870] New: F2FS mount/unmount results in invalid_blkaddr

2024-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218870 Bug ID: 218870 Summary: F2FS mount/unmount results in invalid_blkaddr Product: File System Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: norm

[f2fs-dev] [Bug 218870] F2FS mount/unmount results in invalid_blkaddr

2024-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218870 --- Comment #1 from Patrik Plihal (patrik.pli...@gmail.com) --- It seems to not occur in 6.8.9 (can be downgraded + fsck reissued), I missed this info initially. -- You may reply to this email to add a comment. You are receiving this mail becau

[f2fs-dev] [Bug 218870] F2FS mount/unmount results in invalid_blkaddr

2024-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218870 Paul Gover (pmw.go...@yahoo.co.uk) changed: What|Removed |Added CC||pmw.go...@yahoo.co.uk

[f2fs-dev] [Bug 218870] F2FS mount/unmount results in invalid_blkaddr

2024-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218870 --- Comment #3 from Paul Gover (pmw.go...@yahoo.co.uk) --- Created attachment 306325 --> https://bugzilla.kernel.org/attachment.cgi?id=306325&action=edit syslog showing the problem -- You may reply to this email to add a comment. You are rece

[f2fs-dev] [Bug 218870] F2FS mount/unmount results in invalid_blkaddr

2024-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218870 Jaegeuk Kim (jaeg...@kernel.org) changed: What|Removed |Added CC||jaeg...@kernel.org ---

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #13 from Jaegeuk Kim (jaeg...@kernel.org) --- 6.9.2 will have the fix. https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=b863827181d80ae33f822dc74d32e377737858c2 -- You may reply to this email to add

[f2fs-dev] [Bug 218870] F2FS mount/unmount results in invalid_blkaddr

2024-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218870 Karol Kosek (k...@serenityos.org) changed: What|Removed |Added CC||k...@serenityos.org -

[f2fs-dev] [Bug 218870] F2FS mount/unmount results in invalid_blkaddr

2024-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218870 --- Comment #6 from George Sofianos (geo...@sofianos.dev) --- I did try 6.9.2 (on Arch Linux) and still the same issue. Looking at the commits https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=95d316e2c24a447e2b692

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #14 from Guido (guido.iod...@gmail.com) --- Thank you! -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. ___

[f2fs-dev] [Bug 218770] fsck seems unable to solve corruption

2024-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218770 --- Comment #15 from Jaegeuk Kim (jaeg...@kernel.org) --- correction; 6.9.3-rc1 has the fix. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. __

[f2fs-dev] [Bug 218870] F2FS mount/unmount results in invalid_blkaddr

2024-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218870 --- Comment #7 from Jaegeuk Kim (jaeg...@kernel.org) --- Yeah.. I just saw that Greg queued it in 6.9.3-rc1. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. __

[f2fs-dev] [Bug 218870] F2FS mount/unmount results in invalid_blkaddr

2024-05-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218870 --- Comment #8 from Paul Gover (pmw.go...@yahoo.co.uk) --- Just tried 6.9.3. Appears the fix is now in and working - at least, I booted twice with a short fsck, not the full works - so I'm currently a happy bunny. Thanks. -- You may reply to th

[f2fs-dev] [Bug 218870] F2FS mount/unmount results in invalid_blkaddr

2024-05-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218870 Patrik Plihal (patrik.pli...@gmail.com) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-08-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #49 from YuDong Zhang (mtw...@gmail.com) --- This problem doesn't seem to appear anymore after 5.18.15 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-08-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #50 from Yuriy Garin (yuriy.ga...@gmail.com) --- Created attachment 301543 --> https://bugzilla.kernel.org/attachment.cgi?id=301543&action=edit dmesg log After a month of happy living (see #47) it got me again. $ uname -a Linux xxx

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-08-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #51 from Yuriy Garin (yuriy.ga...@gmail.com) --- Today f2fs_gc got it again just few hours after upgrade to fresh Arch: Linux xxx 5.19.1-arch2-1 #1 SMP PREEMPT_DYNAMIC Thu, 11 Aug 2022 16:06:13 + x86_64 GNU/Linux What I have noti

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-08-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #52 from Yuriy Garin (yuriy.ga...@gmail.com) --- Please, share your experience - how do you deal with this problem? I do 'sudo systemctl poweroff', but, it takes hour, so, after waiting for most services down, I just press power butto

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-08-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #53 from bernd_b (bbutsche...@yahoo.de) --- I'll patch kernel 4.19.1 with debug patch v2 and see if I'll get new debug info. So far, the safest for me is to run my system with kernel < 4.18.x -- You may reply to this email to add a

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-08-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #54 from bernd_b (bbutsche...@yahoo.de) --- I patched kernel 4.19.1 with debug patch v2 but all I can see is that the workload of the cpu goes up to 3.5G and immediately down to 0.8G, and this about every 2 seconds, although there is n

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-08-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 bogdan.nico...@gmail.com changed: What|Removed |Added CC||bogdan.nico...@gmail.com --- C

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-08-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #56 from bogdan.nico...@gmail.com --- Also, there is a another task hanging up with a call trace: kernel: INFO: task mandb:13173 blocked for more than 122 seconds. kernel: Not tainted 5.19.3-arch1-1 #1 kernel: "echo 0 > /proc/sy

[f2fs-dev] [Bug 216285] KASAN: slab-out-of-bounds in mutex_lock and NULL pointer dereference at fs/f2fs/segment.c: f2fs_update_meta_page() when mount a crafted f2fs image

2022-08-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216285 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-09-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 Sebastian Goth (li...@sgoth.de) changed: What|Removed |Added CC||li...@sgoth.de --- Comm

[f2fs-dev] [Bug 216456] New: KASAN: use-after-free in check_index_in_prev_nodes when mount a crafted f2fs image

2022-09-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216456 Bug ID: 216456 Summary: KASAN: use-after-free in check_index_in_prev_nodes when mount a crafted f2fs image Product: File System Version: 2.5 Kernel Version: 5.19.X - 6.0-rc4

[f2fs-dev] [Bug 216285] KASAN: slab-out-of-bounds in mutex_lock and NULL pointer dereference at fs/f2fs/segment.c: f2fs_update_meta_page() when mount a crafted f2fs image

2022-09-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216285 --- Comment #2 from Wenqing Liu (wenqingliu0...@gmail.com) --- Thank you so much. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. _

[f2fs-dev] [Bug 213089] Add "pre: crc32" softdep

2022-09-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213089 Zachary Cook (zachcook1...@gmail.com) changed: What|Removed |Added CC||zachcook1...@gmail

[f2fs-dev] [Bug 216285] KASAN: slab-out-of-bounds in mutex_lock and NULL pointer dereference at fs/f2fs/segment.c: f2fs_update_meta_page() when mount a crafted f2fs image

2022-09-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216285 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|-

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-09-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #58 from Yuriy Garin (yuriy.ga...@gmail.com) --- Created attachment 301840 --> https://bugzilla.kernel.org/attachment.cgi?id=301840&action=edit f2fs debug patch log Applied debug patch v2 to Arch Linux kernel at: 3245cb65fd91 2022-

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-09-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #59 from Yuriy Garin (yuriy.ga...@gmail.com) --- Please forgive my ignorance, I'm sure I'm getting it wrong. How this 'goto repeat' supposed to break a cycle? Here is a simplified code of f2fs_get_lock_data_page(): struct page *f2fs

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-09-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #60 from Yuriy Garin (yuriy.ga...@gmail.com) --- Created attachment 301856 --> https://bugzilla.kernel.org/attachment.cgi?id=301856&action=edit dmesg log Another debug v2 output. Continuation of #58 - without rebooting. This one has

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-09-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #61 from Yuriy Garin (yuriy.ga...@gmail.com) --- Created attachment 301868 --> https://bugzilla.kernel.org/attachment.cgi?id=301868&action=edit dmesg log Another 900 debug patch traces. All on the same address: f2fs_get_lock_data_

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2022-09-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 Zhiguo.Niu (zhiguo@unisoc.com) changed: What|Removed |Added Status|ASSIGNED|RESOLVED Res

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2022-09-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 Zhiguo.Niu (zhiguo@unisoc.com) changed: What|Removed |Added Status|RESOLVED|CLOSED -- You may r

[f2fs-dev] [Bug 216542] New: KASAN: slab-out-of-bounds in fs/f2fs/segment.c:reset_curseg() when mount and operate on crafted image

2022-09-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216542 Bug ID: 216542 Summary: KASAN: slab-out-of-bounds in fs/f2fs/segment.c:reset_curseg() when mount and operate on crafted image Product: File System Version: 2.5

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-10-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #64 from Yuriy Garin (yuriy.ga...@gmail.com) --- Running 6.0.1-arch2-1 for a few days. So far, so good! (Previously, this problem occurred from twice a day to once in a two days.) There were quite a lot of changes in f2fs sources in 6

[f2fs-dev] [Bug 215235] page fault in f2fs_setxattr() when mount and operate on corrupted image

2022-10-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215235 alexwriter (alexwriter2...@gmail.com) changed: What|Removed |Added CC||alexwriter2...@gma

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-10-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #65 from bogdan.nico...@gmail.com --- Unfortunately 6.0.1-arch2-1 didn't do the trick for me. I'm still experiencing this bug, especially when my laptop is coming out of sleep. -- You may reply to this email to add a comment. You ar

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-10-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #66 from Yuriy Garin (yuriy.ga...@gmail.com) --- (In reply to bogdan.nicolae from comment #65) > Unfortunately 6.0.1-arch2-1 didn't do the trick for me. I'm still > experiencing this bug, especially when my laptop is coming out of slee

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-10-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #67 from Yuriy Garin (yuriy.ga...@gmail.com) --- Yes, sadly confirming, this bug happens on 6.0.2-arch1-1: [Mon Oct 24 15:57:09 2022] INFO: task f2fs_ckpt-259:3:273 blocked for more than 122 seconds. [Mon Oct 24 15:57:09 2022] N

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-10-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #68 from bogdan.nico...@gmail.com --- The only reasonable solution that works for me in everyday use is to deactivate the background garbage collector entirely. For reference, this can be done using the background_gc=off mount option (

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-10-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #69 from Matteo Croce (rootki...@yahoo.it) --- That's a terrible workaround. Does it impact the SSD wear leveling algoritmh? Can a periodic fstrim mitigate this? -- You may reply to this email to add a comment. You are receiving th

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-10-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #70 from bogdan.nico...@gmail.com --- Well, if understand correctly, TRIM will still be issued on-demand when segments are cleared. There's also an option background_gc=sync, which I assume will block other I/O operations. Unfortunatel

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #71 from Guido (guido.iod...@gmail.com) --- Since the problem occurred with the 5.18 kernel, I assume there is something wrong after that version. I think the analysis of the problem should start with the changes that occurred with ver

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #72 from Guido (guido.iod...@gmail.com) --- I tried kernel 6.0.6, after 2 days the problem reoccurred :-( -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #73 from Guido (guido.iod...@gmail.com) --- just to try it out, I will now give background_gc=sync a chance -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the b

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #74 from Matteo Croce (rootki...@yahoo.it) --- Hi all, The only way to find where the issue is, is to bisect from the latest working kernel to the first non working one -- You may reply to this email to add a comment. You are recei

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #75 from bogdan.nico...@gmail.com --- Guido just pointed that out in #71: the issue appeared since 5.18 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #76 from Guido (guido.iod...@gmail.com) --- (In reply to Matteo Croce from comment #74) > Hi all, > > The only way to find where the issue is, is to bisect from the latest > working kernel to the first non working one the last workin

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #77 from Matteo Croce (rootki...@yahoo.it) --- Great. If you do a bisect, you will find the problem in, let's say, 14 steps. Really worth a try. -- You may reply to this email to add a comment. You are receiving this mail because: Y

[f2fs-dev] [Bug 216669] New: f2fs inconsistent node block when executing f2fs_fill_super

2022-11-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216669 Bug ID: 216669 Summary: f2fs inconsistent node block when executing f2fs_fill_super Product: File System Version: 2.5 Kernel Version: 5.10 Hardware: ARM

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #78 from Guido (guido.iod...@gmail.com) --- I tried background_gc=sync. It doesn't solve the problem... -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #79 from Jaegeuk Kim (jaeg...@kernel.org) --- I just had some time to think of this issue, and suspect there was no time to reschedule the cpu in the loop? Can anyone try this change? diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c inde

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #80 from Guido (guido.iod...@gmail.com) --- (In reply to Jaegeuk Kim from comment #79) I tried to apply it to kernel 6.0.8 but failed. I found the code at row 1313 so I can try to apply there. But there is another identical code at ro

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #81 from Jaegeuk Kim (jaeg...@kernel.org) --- I think 1313 would be enough to avoid this issue first. 3568 case is after submit IO which could have a chance to get another states. -- You may reply to this email to add a comment. You

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #82 from Guido (guido.iod...@gmail.com) --- (In reply to Jaegeuk Kim from comment #81) > I think 1313 would be enough to avoid this issue first. > 3568 case is after submit IO which could have a chance to get another states. Thank you

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #83 from Guido (guido.iod...@gmail.com) --- I tried this script to trigger the GC: https://github.com/LLJY/f2fs-gc/blob/master/f2fs-gc.sh It's been running for 10 minutes now, but it's stock to 2503 dirty segments on the root partitio

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #84 from Guido (guido.iod...@gmail.com) --- this is the output Performing GC on /sys/fs/f2fs/nvme0n1p3/ 2589 2589 2503 2503 2503 2503 ... and a lot of 2503 -- You may reply to this email to add a comment. You are receiving thi

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #85 from Guido (guido.iod...@gmail.com) --- I modified the script to run it on the partition on my choice. No problem with the home and other partitions. It looks like something in root partition. May be it is related to the bug? --

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #86 from Yuriy Garin (yuriy.ga...@gmail.com) --- (In reply to Jaegeuk Kim from comment #79) Running this patch (and debug printk) on 6.0.8-arch1-1. -- You may reply to this email to add a comment. You are receiving this mail becaus

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #87 from Guido (guido.iod...@gmail.com) --- Created attachment 303184 --> https://bugzilla.kernel.org/attachment.cgi?id=303184&action=edit kernel log (with patch on data.c applied) -- You may reply to this email to add a comment.

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #88 from Guido (guido.iod...@gmail.com) --- (In reply to Guido from comment #87) > Created attachment 303184 [details] > kernel log (with patch on data.c applied) After several days of use I still did not have the 100% cpu busy proble

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #89 from bogdan.nico...@gmail.com --- I confirm the bug persists both with background_gc=on and background_gc=sync. It's especially prone to manifest when the machine is idle for a long time. It almost feels like the gc hangs because i

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #90 from Guido (guido.iod...@gmail.com) --- > diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c > index a71e818cd67b..c351c3269874 100644 > --- a/fs/f2fs/data.c > +++ b/fs/f2fs/data.c > @@ -1325,6 +1325,7 @@ struct page *f2fs_get_lock_data_

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #91 from Yuriy Garin (yuriy.ga...@gmail.com) --- Created attachment 303300 --> https://bugzilla.kernel.org/attachment.cgi?id=303300&action=edit debug patch with f2fs_io_schedule_timeout (In reply to #79) This debug patch adds f2fs_

[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

2022-11-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #92 from Yuriy Garin (yuriy.ga...@gmail.com) --- Created attachment 303301 --> https://bugzilla.kernel.org/attachment.cgi?id=303301&action=edit dmesg log for patch f2fs_io_schedule_timeout #91 As you see, there is a lot of lines "ba

  1   2   3   4   5   6   7   8   >