I noticed my system has a hung process trying to 'rmmod nf_conntrack'.
I've generally been doing the script that calls rmmod forever,
but only extensively tested on 5.4 kernel and earlier.
If anyone has any ideas, please let me know. This is from 'sysrq t'. I don't
see
any hung-task splats in dmesg. I'll see if it is reproducible and if so will
try
with lockdep enabled...
21497 Jan 07 16:12:05 TR-398 kernel: task:rmmod state:R running task
stack: 0 pid: 4107 ppid: 4054 flags:0x00004084
21498 Jan 07 16:12:05 TR-398 kernel: Call Trace:
21499 Jan 07 16:12:05 TR-398 kernel: ? do_softirq_own_stack+0x32/0x40
21500 Jan 07 16:12:05 TR-398 kernel: ? irq_exit_rcu+0x39/0x90
21501 Jan 07 16:12:05 TR-398 kernel: ? sysvec_apic_timer_interrupt+0x34/0x80
21502 Jan 07 16:12:05 TR-398 kernel: ?
asm_sysvec_apic_timer_interrupt+0x12/0x20
21503 Jan 07 16:12:05 TR-398 kernel: ? nf_conntrack_attach+0x30/0x30
[nf_conntrack]
21504 Jan 07 16:12:05 TR-398 kernel: ? _raw_spin_lock+0x12/0x20
21505 Jan 07 16:12:05 TR-398 kernel: ? do_softirq_own_stack+0x32/0x40
21506 Jan 07 16:12:05 TR-398 kernel: ? nf_conntrack_lock+0x9/0x40
[nf_conntrack]
21507 Jan 07 16:12:05 TR-398 kernel: ? nf_ct_iterate_cleanup+0x88/0x140
[nf_conntrack]
21508 Jan 07 16:12:05 TR-398 kernel: ? nf_conntrack_cleanup_net_list+0x36/0xc0
[nf_conntrack]
21509 Jan 07 16:12:05 TR-398 kernel: ? unregister_pernet_operations+0xcc/0x130
21510 Jan 07 16:12:05 TR-398 kernel: ? unregister_pernet_subsys+0x18/0x30
21511 Jan 07 16:12:05 TR-398 kernel: ? nf_conntrack_standalone_fini+0x11/0x425
[nf_conntrack]
21512 Jan 07 16:12:05 TR-398 kernel: ? __x64_sys_delete_module+0x131/0x270
21513 Jan 07 16:12:05 TR-398 kernel: ? syscall_trace_enter.isra.21+0xf9/0x190
21514 Jan 07 16:12:05 TR-398 kernel: ? do_syscall_64+0x2d/0x70
21515 Jan 07 16:12:05 TR-398 kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
Thanks,
Ben
--
Ben Greear <gree...@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
