[v6.1] INFO: task hung in deactivate_super
5 views
Skip to first unread message
syzbot
Jun 30, 2023, 6:50:03 AM6/30/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: a1c449d00ff8 Linux 6.1.36
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=121bf634a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=18d0811d410fac65
dashboard link: https://syzkaller.appspot.com/bug?extid=903fb24bb290b01a6054
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1af4dd87a7c3/disk-a1c449d0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cb6c9d322fca/vmlinux-a1c449d0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cab3d4d89c94/bzImage-a1c449d0.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+903fb2...@syzkaller.appspotmail.com
INFO: task syz-executor.1:3588 blocked for more than 143 seconds.
Not tainted 6.1.36-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:20536 pid:3588 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
rwsem_down_write_slowpath+0xe93/0x14a0 kernel/locking/rwsem.c:1189
deactivate_super+0xa9/0xe0 fs/super.c:362
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xd9/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f26e1a8d7f7
RSP: 002b:00007ffced1c5b18 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f26e1a8d7f7
RDX: 00007ffced1c5cdf RSI: 000000000000000a RDI: 00007ffced1c5be0
RBP: 00007ffced1c5be0 R08: 000000000000000f R09: 00007ffced1c59b0
R10: 0000555556d81873 R11: 0000000000000246 R12: 00007f26e1ad643b
R13: 00007ffced1c6ca0 R14: 0000555556d81810 R15: 00007ffced1c6ce0
</TASK>
INFO: task syz-executor.5:23874 blocked for more than 143 seconds.
Not tainted 6.1.36-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:24136 pid:23874 ppid:3595 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
jfs_flush_journal+0x72b/0xec0 fs/jfs/jfs_logmgr.c:1564
jfs_sync_fs+0x7c/0xa0 fs/jfs/super.c:684
iterate_supers+0x127/0x1e0 fs/super.c:746
ksys_sync+0xd7/0x1c0 fs/sync.c:104
__do_sys_sync+0xa/0x10 fs/sync.c:113
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f013648c389
RSP: 002b:00007f01372b3168 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007f01365abf80 RCX: 00007f013648c389
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007f01364d7493 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd73e72c8f R14: 00007f01372b3300 R15: 0000000000022000
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cf27470 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cf27c70 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
#0: ffffffff8cf272a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3300:
#0: ffff8880292ac098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2177
1 lock held by syz-executor.1/3588:
#0: ffff8880915b20e0 (&type->s_umount_key#76){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:362
2 locks held by kworker/u4:17/2300:
2 locks held by kworker/u4:18/2302:
1 lock held by syz-executor.5/23874:
#0: ffff8880915b20e0 (&type->s_umount_key#76){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:744
1 lock held by syz-executor.2/23915:
#0: ffff8880915b20e0 (&type->s_umount_key#76){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:744
1 lock held by syz-executor.5/23944:
#0: ffff8880915b20e0 (&type->s_umount_key#76){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:744
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.36-syzkaller #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+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf18/0xf60 kernel/hung_task.c:377
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 8098 Comm: kworker/u4:12 Not tainted 6.1.36-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:29 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:130 [inline]
RIP: 0010:lock_acquire+0x23e/0x5a0 kernel/locking/lockdep.c:5672
Code: 7e 83 f8 01 0f 85 a4 01 00 00 49 89 de 48 c1 eb 03 42 80 3c 2b 00 74 08 4c 89 f7 e8 0c 63 76 00 48 c7 44 24 60 00 00 00 00 9c <8f> 44 24 60 42 80 3c 2b 00 74 08 4c 89 f7 e8 6f 62 76 00 f6 44 24
RSP: 0018:ffffc9000b767a78 EFLAGS: 00000046
RAX: 0000000000000001 RBX: 1ffff920016ecf5c RCX: 1ffff920016ecefc
RDX: dffffc0000000000 RSI: ffffffff8aebe320 RDI: ffffffff8b3ccd20
RBP: ffffc9000b767bd8 R08: dffffc0000000000 R09: fffffbfff2051845
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff920016ecf58
R13: dffffc0000000000 R14: ffffc9000b767ae0 R15: 0000000000000246
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c002827000 CR3: 000000000cc8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 000000000000003b DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:306
rcu_read_lock include/linux/rcupdate.h:747 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:408 [inline]
batadv_nc_worker+0xc1/0x5b0 net/batman-adv/network-coding.c:719
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: a1c449d00ff8 Linux 6.1.36
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=121bf634a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=18d0811d410fac65
dashboard link: https://syzkaller.appspot.com/bug?extid=903fb24bb290b01a6054
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1af4dd87a7c3/disk-a1c449d0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cb6c9d322fca/vmlinux-a1c449d0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cab3d4d89c94/bzImage-a1c449d0.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+903fb2...@syzkaller.appspotmail.com
INFO: task syz-executor.1:3588 blocked for more than 143 seconds.
Not tainted 6.1.36-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:20536 pid:3588 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
rwsem_down_write_slowpath+0xe93/0x14a0 kernel/locking/rwsem.c:1189
deactivate_super+0xa9/0xe0 fs/super.c:362
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xd9/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f26e1a8d7f7
RSP: 002b:00007ffced1c5b18 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f26e1a8d7f7
RDX: 00007ffced1c5cdf RSI: 000000000000000a RDI: 00007ffced1c5be0
RBP: 00007ffced1c5be0 R08: 000000000000000f R09: 00007ffced1c59b0
R10: 0000555556d81873 R11: 0000000000000246 R12: 00007f26e1ad643b
R13: 00007ffced1c6ca0 R14: 0000555556d81810 R15: 00007ffced1c6ce0
</TASK>
INFO: task syz-executor.5:23874 blocked for more than 143 seconds.
Not tainted 6.1.36-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:24136 pid:23874 ppid:3595 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
jfs_flush_journal+0x72b/0xec0 fs/jfs/jfs_logmgr.c:1564
jfs_sync_fs+0x7c/0xa0 fs/jfs/super.c:684
iterate_supers+0x127/0x1e0 fs/super.c:746
ksys_sync+0xd7/0x1c0 fs/sync.c:104
__do_sys_sync+0xa/0x10 fs/sync.c:113
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f013648c389
RSP: 002b:00007f01372b3168 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007f01365abf80 RCX: 00007f013648c389
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007f01364d7493 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd73e72c8f R14: 00007f01372b3300 R15: 0000000000022000
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cf27470 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cf27c70 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
#0: ffffffff8cf272a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3300:
#0: ffff8880292ac098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2177
1 lock held by syz-executor.1/3588:
#0: ffff8880915b20e0 (&type->s_umount_key#76){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:362
2 locks held by kworker/u4:17/2300:
2 locks held by kworker/u4:18/2302:
1 lock held by syz-executor.5/23874:
#0: ffff8880915b20e0 (&type->s_umount_key#76){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:744
1 lock held by syz-executor.2/23915:
#0: ffff8880915b20e0 (&type->s_umount_key#76){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:744
1 lock held by syz-executor.5/23944:
#0: ffff8880915b20e0 (&type->s_umount_key#76){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:744
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.36-syzkaller #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+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf18/0xf60 kernel/hung_task.c:377
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 8098 Comm: kworker/u4:12 Not tainted 6.1.36-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:29 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:130 [inline]
RIP: 0010:lock_acquire+0x23e/0x5a0 kernel/locking/lockdep.c:5672
Code: 7e 83 f8 01 0f 85 a4 01 00 00 49 89 de 48 c1 eb 03 42 80 3c 2b 00 74 08 4c 89 f7 e8 0c 63 76 00 48 c7 44 24 60 00 00 00 00 9c <8f> 44 24 60 42 80 3c 2b 00 74 08 4c 89 f7 e8 6f 62 76 00 f6 44 24
RSP: 0018:ffffc9000b767a78 EFLAGS: 00000046
RAX: 0000000000000001 RBX: 1ffff920016ecf5c RCX: 1ffff920016ecefc
RDX: dffffc0000000000 RSI: ffffffff8aebe320 RDI: ffffffff8b3ccd20
RBP: ffffc9000b767bd8 R08: dffffc0000000000 R09: fffffbfff2051845
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff920016ecf58
R13: dffffc0000000000 R14: ffffc9000b767ae0 R15: 0000000000000246
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c002827000 CR3: 000000000cc8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 000000000000003b DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:306
rcu_read_lock include/linux/rcupdate.h:747 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:408 [inline]
batadv_nc_worker+0xc1/0x5b0 net/batman-adv/network-coding.c:719
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Nov 26, 2023, 7:17:14 AM11/26/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages