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

2022-12-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #94 from Yuriy Garin (yuriy.ga...@gmail.com) --- (In reply to Yuriy Garin from comment #93) > It's running on 6.0.9-arch1-1: > > $ uname -a > Linux ... 6.0.9-arch1-1 #2 SMP PREEMPT_DYNAMIC Wed, 23 Nov 2022 05:14:08 > + x86_64 GNU/

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

2022-12-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #95 from Yuriy Garin (yuriy.ga...@gmail.com) --- May be it worth to inject printk "upstream", to see where this condition page->mapping != mapping happens at first place? Any ideas? -- You may reply to this email to add a comment.

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

2022-12-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #96 from bogdan.nico...@gmail.com --- Well there's also a possibility that the mapping of the inode changes since it was initialized in the beginning: struct address_space *mapping = inode->i_mapping; How about printing all three: pag

[f2fs-dev] [PATCH v2] f2fs: don't call f2fs_issue_discard_timeout() when discard_cmd_cnt is 0 in f2fs_put_super()

2022-12-01 Thread Yangtao Li via Linux-f2fs-devel
No need to call f2fs_issue_discard_timeout() in f2fs_put_super, when no discard command requires issue. Since the caller of f2fs_issue_discard_timeout() usually judges the number of discard commands before using it. Let's move this logic to f2fs_issue_discard_timeout(). By the way, use f2fs_realti

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

2022-12-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #97 from Yuriy Garin (yuriy.ga...@gmail.com) --- (In reply to bogdan.nicolae from comment #96) > Well there's also a possibility that the mapping of the inode changes since > it was initialized in the beginning: > struct address_space

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

2022-12-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216050 --- Comment #98 from Yuriy Garin (yuriy.ga...@gmail.com) --- It would be funny, if actually inode->i_mapping was correctly fixed already, and we spin for nothing. :) -- You may reply to this email to add a comment. You are receiving this mail