Bugzilla – Bug 1221884
Kernel panics kworker/3:2
Last modified: 2024-04-19 13:55:59 UTC
Over the past few weeks I've been suffering from kernel panics so I setup `kdump`. Today I had another kernel panic and using crash I have gotten a backtrace ``` PID: 4288 TASK: ffff8e18c865af40 CPU: 3 COMMAND: "kworker/3:2" #0 [ffffabe5a583fb48] machine_kexec at ffffffffa108fe0f #1 [ffffabe5a583fba0] __crash_kexec at ffffffffa11c7e0e #2 [ffffabe5a583fc60] crash_kexec at ffffffffa11c92a4 #3 [ffffabe5a583fc68] oops_end at ffffffffa10457c4 #4 [ffffabe5a583fc88] page_fault_oops at ffffffffa10a53f1 #5 [ffffabe5a583fd08] exc_page_fault at ffffffffa1ccfc21 #6 [ffffabe5a583fd30] asm_exc_page_fault at ffffffffa1e012a6 [exception RIP: rb_first+15] RIP: ffffffffa1cb7a8f RSP: ffffabe5a583fde0 RFLAGS: 00010206 RAX: 0000000000003593 RBX: ffff8e18842b7780 RCX: ffffcd4cdc678a90 RDX: 0000000000003593 RSI: 0000000000000000 RDI: ffff8e1886681498 RBP: ffff8e22b4bd9d80 R8: 0000000000000246 R9: 00000000010000ff R10: 00000000010000ff R11: fefefefefefefeff R12: 0000000000000000 R13: ffff8e1886681498 R14: ffff8e19216b3000 R15: ffff8e18817e8ab0 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000 #7 [ffffabe5a583fde0] simple_xattrs_free at ffffffffa1453ba9 #8 [ffffabe5a583fe08] kernfs_put at ffffffffa14dd160 #9 [ffffabe5a583fe30] css_free_rwork_fn at ffffffffa11d59d5 #10 [ffffabe5a583fe68] process_one_work at ffffffffa10e8635 #11 [ffffabe5a583fea8] worker_thread at ffffffffa10e97e5 #12 [ffffabe5a583fef8] kthread at ffffffffa10f38c5 #13 [ffffabe5a583ff30] ret_from_fork at ffffffffa1050f41 #14 [ffffabe5a583ff50] ret_from_fork_asm at ffffffffa100383b ``` Please inform me if more information/data is required I will do my best to provide it
looks like another instance of bsc#1220814
I think upstream commit 4207b556e62f ("kernfs: RCU protect kernfs_nodes and avoid kernfs_idr_lock in kernfs_find_and_get_node_by_id()") fixes this issue, and this was backported to v6.8.6 which is now available in TW. Could you please give it a try and see if this is still reproducible?
closing as dup of 1220814. *** This bug has been marked as a duplicate of bug 1220814 ***