[v5.15] INFO: task hung in lmLogClose
0 views
Skip to first unread message
syzbot
Apr 5, 2024, 7:21:34 AMApr 5
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 9465fef4ae35 Linux 5.15.153
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10d67ead180000
kernel config: https://syzkaller.appspot.com/x/.config?x=176c746ee3348b33
dashboard link: https://syzkaller.appspot.com/bug?extid=f6eb2331cbd10f200097
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2962c02652ce/disk-9465fef4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d0f5a1ce082d/vmlinux-9465fef4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/86b5b1eea636/bzImage-9465fef4.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f6eb23...@syzkaller.appspotmail.com
INFO: task syz-executor.1:22746 blocked for more than 143 seconds.
Not tainted 5.15.153-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:20864 pid:22746 ppid: 1 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
jfs_umount+0x298/0x370 fs/jfs/jfs_umount.c:116
jfs_put_super+0x86/0x180 fs/jfs/super.c:194
generic_shutdown_super+0x136/0x2c0 fs/super.c:475
kill_block_super+0x7a/0xe0 fs/super.c:1414
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1bac98e197
RSP: 002b:00007ffea15d75c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f1bac98e197
RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007ffea15d7680
RBP: 00007ffea15d7680 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffea15d8740
R13: 00007f1bac9d83b9 R14: 00000000000cde2c R15: 0000000000000009
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c91f720 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3262:
#0: ffff8880248cb098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bad2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
4 locks held by kworker/1:21/12267:
#0: ffff8880b9b3a318 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
#1: ffff8880b9b27848 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x4e1/0x810 kernel/sched/psi.c:882
#2: ffff88807c3f8d60 (&r->consumer_lock#2){+.+.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:368 [inline]
#2: ffff88807c3f8d60 (&r->consumer_lock#2){+.+.}-{2:2}, at: ptr_ring_consume_bh include/linux/ptr_ring.h:365 [inline]
#2: ffff88807c3f8d60 (&r->consumer_lock#2){+.+.}-{2:2}, at: wg_packet_encrypt_worker+0x1233/0x1590 drivers/net/wireguard/send.c:293
#3: ffff8880b9b28098 (&base->lock){-.-.}-{2:2}, at: __mod_timer+0x772/0xeb0 kernel/time/timer.c:1043
2 locks held by syz-executor.0/18334:
#0: ffff8880796e60e0 (&type->s_umount_key#73){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
#1: ffffffff8ccb0c08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
2 locks held by syz-executor.4/21019:
#0: ffff88801d0cc0e0 (&type->s_umount_key#73){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
#1: ffffffff8ccb0c08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
2 locks held by syz-executor.1/22746:
#0: ffff8880229520e0 (&type->s_umount_key#73){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
#1: ffffffff8ccb0c08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
1 lock held by syz-executor.2/22856:
#0: ffff888050be00e0 (&type->s_umount_key#73){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.153-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 15416 Comm: kworker/u4:17 Not tainted 5.15.153-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: phy5 ieee80211_iface_work
RIP: 0010:stack_trace_consume_entry+0x7/0x270 kernel/stacktrace.c:83
Code: 80 c1 03 38 c1 0f 8c 7b ff ff ff 48 89 df e8 70 25 5c 00 e9 6e ff ff ff e8 c6 25 ae 08 66 0f 1f 44 00 00 55 41 57 41 56 41 55 <41> 54 53 48 83 ec 18 48 89 fb 48 ba 00 00 00 00 00 fc ff df 4c 8d
RSP: 0018:ffffc90003506f78 EFLAGS: 00000286
RAX: ffffffff810054af RBX: ffffc90003506fa0 RCX: 0000000080000201
RDX: dffffc0000000000 RSI: ffffffff810054af RDI: ffffc90003507080
RBP: ffffc90003507030 R08: ffffc90003507f48 R09: ffffc90003506ff0
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880196a0000
R13: ffffffff816dd330 R14: ffffc90003507080 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f13b1ec4580 CR3: 000000007adcb000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: fffffffffffffff8 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
arch_stack_walk+0x101/0x140 arch/x86/kernel/stacktrace.c:27
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack+0x36/0x60 mm/kasan/common.c:38
kasan_record_aux_stack+0xba/0x100 mm/kasan/generic.c:348
kvfree_call_rcu+0x118/0x8a0 kernel/rcu/tree.c:3596
cfg80211_update_known_bss+0x16b/0x9e0
cfg80211_bss_update+0x187/0x21e0 net/wireless/scan.c:1771
cfg80211_inform_single_bss_frame_data net/wireless/scan.c:2492 [inline]
cfg80211_inform_bss_frame_data+0xa13/0x20f0 net/wireless/scan.c:2525
ieee80211_bss_info_update+0x7a6/0xc80 net/mac80211/scan.c:190
ieee80211_rx_bss_info net/mac80211/ibss.c:1123 [inline]
ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1614 [inline]
ieee80211_ibss_rx_queued_mgmt+0x175e/0x2af0 net/mac80211/ibss.c:1643
ieee80211_iface_process_skb net/mac80211/iface.c:1441 [inline]
ieee80211_iface_work+0x78f/0xcc0 net/mac80211/iface.c:1495
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, 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: 9465fef4ae35 Linux 5.15.153
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10d67ead180000
kernel config: https://syzkaller.appspot.com/x/.config?x=176c746ee3348b33
dashboard link: https://syzkaller.appspot.com/bug?extid=f6eb2331cbd10f200097
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2962c02652ce/disk-9465fef4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d0f5a1ce082d/vmlinux-9465fef4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/86b5b1eea636/bzImage-9465fef4.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f6eb23...@syzkaller.appspotmail.com
INFO: task syz-executor.1:22746 blocked for more than 143 seconds.
Not tainted 5.15.153-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:20864 pid:22746 ppid: 1 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
jfs_umount+0x298/0x370 fs/jfs/jfs_umount.c:116
jfs_put_super+0x86/0x180 fs/jfs/super.c:194
generic_shutdown_super+0x136/0x2c0 fs/super.c:475
kill_block_super+0x7a/0xe0 fs/super.c:1414
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1bac98e197
RSP: 002b:00007ffea15d75c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f1bac98e197
RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007ffea15d7680
RBP: 00007ffea15d7680 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffea15d8740
R13: 00007f1bac9d83b9 R14: 00000000000cde2c R15: 0000000000000009
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c91f720 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3262:
#0: ffff8880248cb098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bad2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
4 locks held by kworker/1:21/12267:
#0: ffff8880b9b3a318 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
#1: ffff8880b9b27848 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x4e1/0x810 kernel/sched/psi.c:882
#2: ffff88807c3f8d60 (&r->consumer_lock#2){+.+.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:368 [inline]
#2: ffff88807c3f8d60 (&r->consumer_lock#2){+.+.}-{2:2}, at: ptr_ring_consume_bh include/linux/ptr_ring.h:365 [inline]
#2: ffff88807c3f8d60 (&r->consumer_lock#2){+.+.}-{2:2}, at: wg_packet_encrypt_worker+0x1233/0x1590 drivers/net/wireguard/send.c:293
#3: ffff8880b9b28098 (&base->lock){-.-.}-{2:2}, at: __mod_timer+0x772/0xeb0 kernel/time/timer.c:1043
2 locks held by syz-executor.0/18334:
#0: ffff8880796e60e0 (&type->s_umount_key#73){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
#1: ffffffff8ccb0c08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
2 locks held by syz-executor.4/21019:
#0: ffff88801d0cc0e0 (&type->s_umount_key#73){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
#1: ffffffff8ccb0c08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
2 locks held by syz-executor.1/22746:
#0: ffff8880229520e0 (&type->s_umount_key#73){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
#1: ffffffff8ccb0c08 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
1 lock held by syz-executor.2/22856:
#0: ffff888050be00e0 (&type->s_umount_key#73){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.153-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 15416 Comm: kworker/u4:17 Not tainted 5.15.153-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: phy5 ieee80211_iface_work
RIP: 0010:stack_trace_consume_entry+0x7/0x270 kernel/stacktrace.c:83
Code: 80 c1 03 38 c1 0f 8c 7b ff ff ff 48 89 df e8 70 25 5c 00 e9 6e ff ff ff e8 c6 25 ae 08 66 0f 1f 44 00 00 55 41 57 41 56 41 55 <41> 54 53 48 83 ec 18 48 89 fb 48 ba 00 00 00 00 00 fc ff df 4c 8d
RSP: 0018:ffffc90003506f78 EFLAGS: 00000286
RAX: ffffffff810054af RBX: ffffc90003506fa0 RCX: 0000000080000201
RDX: dffffc0000000000 RSI: ffffffff810054af RDI: ffffc90003507080
RBP: ffffc90003507030 R08: ffffc90003507f48 R09: ffffc90003506ff0
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880196a0000
R13: ffffffff816dd330 R14: ffffc90003507080 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f13b1ec4580 CR3: 000000007adcb000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: fffffffffffffff8 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
arch_stack_walk+0x101/0x140 arch/x86/kernel/stacktrace.c:27
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack+0x36/0x60 mm/kasan/common.c:38
kasan_record_aux_stack+0xba/0x100 mm/kasan/generic.c:348
kvfree_call_rcu+0x118/0x8a0 kernel/rcu/tree.c:3596
cfg80211_update_known_bss+0x16b/0x9e0
cfg80211_bss_update+0x187/0x21e0 net/wireless/scan.c:1771
cfg80211_inform_single_bss_frame_data net/wireless/scan.c:2492 [inline]
cfg80211_inform_bss_frame_data+0xa13/0x20f0 net/wireless/scan.c:2525
ieee80211_bss_info_update+0x7a6/0xc80 net/mac80211/scan.c:190
ieee80211_rx_bss_info net/mac80211/ibss.c:1123 [inline]
ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1614 [inline]
ieee80211_ibss_rx_queued_mgmt+0x175e/0x2af0 net/mac80211/ibss.c:1643
ieee80211_iface_process_skb net/mac80211/iface.c:1441 [inline]
ieee80211_iface_work+0x78f/0xcc0 net/mac80211/iface.c:1495
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages