syzbot


INFO: task hung in init_module_from_file

Status: auto-obsoleted due to no activity on 2023/08/28 09:43
Subsystems: modules
[Documentation on labels]
First crash: 784d, last: 775d

Sample crash report:
INFO: task syz-executor.2:8231 blocked for more than 143 seconds.
      Not tainted 6.4.0-syzkaller-11312-gb5641a5d8b8b #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2  state:D stack:27800 pid:8231  ppid:5052   flags:0x00000004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0xc9a/0x5880 kernel/sched/core.c:6710
 schedule+0xde/0x1a0 kernel/sched/core.c:6786
 schedule_timeout+0x276/0x2b0 kernel/time/timer.c:2143
 do_wait_for_common kernel/sched/completion.c:85 [inline]
 __wait_for_common+0x1ce/0x5c0 kernel/sched/completion.c:106
 init_module_from_file+0x300/0x6a0 kernel/module/main.c:3125
 __do_sys_finit_module kernel/module/main.c:3171 [inline]
 __se_sys_finit_module kernel/module/main.c:3154 [inline]
 __x64_sys_finit_module+0xfd/0x190 kernel/module/main.c:3154
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fa19328c389
RSP: 002b:00007fa193ff3168 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
RAX: ffffffffffffffda RBX: 00007fa1933abf80 RCX: 00007fa19328c389
RDX: 0000000000000002 RSI: 0000000020000380 RDI: 0000000000000004
RBP: 00007fa1932d7493 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffdf8562e8f R14: 00007fa193ff3300 R15: 0000000000022000
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8c9a1af0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0xd80 kernel/rcu/tasks.h:522
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8c9a17f0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0xd80 kernel/rcu/tasks.h:522
1 lock held by khungtaskd/28:
 #0: ffffffff8c9a2700 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x340 kernel/locking/lockdep.c:6615
2 locks held by getty/4767:
 #0: ffff888028b86098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x26/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc900015c02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xf08/0x13f0 drivers/tty/n_tty.c:2187
2 locks held by kworker/u4:0/12936:
 #0: ffff8880b993c3d8 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2f/0x120 kernel/sched/core.c:558
 #1: ffff8880b9928848 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x216/0x950 kernel/sched/psi.c:983

=============================================

NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.4.0-syzkaller-11312-gb5641a5d8b8b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x29c/0x350 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x2a4/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xe16/0x1090 kernel/hung_task.c:379
 kthread+0x344/0x440 kernel/kthread.c:389
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 12919 Comm: syz-executor.3 Not tainted 6.4.0-syzkaller-11312-gb5641a5d8b8b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RISeaBIOS (version 1.8.2-google)

Crashes (19):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/07/04 23:35 upstream b5641a5d8b8b 17a98177 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in init_module_from_file
2023/07/04 14:46 upstream 24be4d0b46bb 6e553898 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in init_module_from_file
2023/07/04 12:32 upstream 24be4d0b46bb 6e553898 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in init_module_from_file
2023/07/03 12:23 upstream a901a3568fd2 bfc47836 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in init_module_from_file
2023/07/03 01:27 upstream 995b406c7e97 bfc47836 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in init_module_from_file
2023/07/03 00:07 upstream 995b406c7e97 bfc47836 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in init_module_from_file
2023/07/02 21:11 upstream 995b406c7e97 bfc47836 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in init_module_from_file
2023/07/02 18:40 upstream 995b406c7e97 bfc47836 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in init_module_from_file
2023/07/02 18:18 upstream 995b406c7e97 bfc47836 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in init_module_from_file
2023/07/02 05:58 upstream f8566aa4f176 bfc47836 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in init_module_from_file
2023/07/02 00:51 upstream f8566aa4f176 bfc47836 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in init_module_from_file
2023/07/01 16:27 upstream b25f62ccb490 af3053d2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in init_module_from_file
2023/07/01 15:37 upstream b25f62ccb490 af3053d2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in init_module_from_file
2023/07/01 13:07 upstream b25f62ccb490 af3053d2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in init_module_from_file
2023/07/01 12:54 upstream b25f62ccb490 af3053d2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in init_module_from_file
2023/07/05 01:26 linux-next 1c6f93977947 17a98177 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in init_module_from_file
2023/07/04 10:35 linux-next 1c6f93977947 6e553898 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in init_module_from_file
2023/06/30 13:42 linux-next 6352a698ca5b 01298212 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in init_module_from_file
2023/07/09 09:37 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 533925cb7604 668cb1fa .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-riscv64 INFO: task hung in init_module_from_file
* Struck through repros no longer work on HEAD.