I wonder if this is/was solved by this commit: https://github.com/torvalds/linux/commit/e1b849cfa6b61f1c866a908c9e8dd9b5aaab820b
2025-09 writeback: Avoid contention on wb->list_lock when switching inodes Or at least some versions of this error.. specifically the cgroup/inode switching one identified here: https://dasl.cc/2025/01/01/debugging-our-new-linux-kernel/#whats-causing-elevated-system-cpu It's possible there are other causes of inode_switch_wbs_work_fn getting stuck, you'd have to check perf/flamegraph. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038492 Title: workqueue: inode_switch_wbs_work_fn hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038492/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
