[v5.15] INFO: task hung in unix_stream_sendmsg
2 views
Skip to first unread message
syzbot
Mar 2, 2024, 2:56:23 PMMar 2
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 80efc6265290 Linux 5.15.150
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14eb1c6a180000
kernel config: https://syzkaller.appspot.com/x/.config?x=928a06454760df60
dashboard link: https://syzkaller.appspot.com/bug?extid=81e4eaace743ea8b0379
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/178c37e05837/disk-80efc626.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c9672d0d3f85/vmlinux-80efc626.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3e859ffa360e/bzImage-80efc626.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+81e4ea...@syzkaller.appspotmail.com
INFO: task syz-executor.3:28905 blocked for more than 143 seconds.
Not tainted 5.15.150-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:27520 pid:28905 ppid: 20563 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
wait_for_unix_gc+0x14e/0x210 net/unix/garbage.c:201
unix_stream_sendmsg+0xc3/0x1070 net/unix/af_unix.c:2035
sock_sendmsg_nosec net/socket.c:704 [inline]
__sock_sendmsg net/socket.c:716 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2431
___sys_sendmsg+0x252/0x2e0 net/socket.c:2485
__sys_sendmsg net/socket.c:2514 [inline]
__do_sys_sendmsg net/socket.c:2523 [inline]
__se_sys_sendmsg+0x19a/0x260 net/socket.c:2521
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+0x61/0xcb
RIP: 0033:0x7f54b4a51da9
RSP: 002b:00007f54b2fd20c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f54b4b7ff80 RCX: 00007f54b4a51da9
RDX: 0000000020000001 RSI: 00000000200002c0 RDI: 0000000000000003
RBP: 00007f54b4a9e47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f54b4b7ff80 R15: 00007fff3fd33958
</TASK>
INFO: task syz-executor.0:28920 blocked for more than 143 seconds.
Not tainted 5.15.150-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:27712 pid:28920 ppid: 21633 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
wait_for_unix_gc+0x14e/0x210 net/unix/garbage.c:201
unix_stream_sendmsg+0xc3/0x1070 net/unix/af_unix.c:2035
sock_sendmsg_nosec net/socket.c:704 [inline]
__sock_sendmsg net/socket.c:716 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2431
___sys_sendmsg+0x252/0x2e0 net/socket.c:2485
__sys_sendmsg net/socket.c:2514 [inline]
__do_sys_sendmsg net/socket.c:2523 [inline]
__se_sys_sendmsg+0x19a/0x260 net/socket.c:2521
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+0x61/0xcb
RIP: 0033:0x7f8462d12da9
RSP: 002b:00007f84612930c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f8462e40f80 RCX: 00007f8462d12da9
RDX: 0000000020000001 RSI: 00000000200002c0 RDI: 0000000000000003
RBP: 00007f8462d5f47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f8462e40f80 R15: 00007ffc5a3c9898
</TASK>
INFO: task syz-executor.2:28942 blocked for more than 144 seconds.
Not tainted 5.15.150-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:27776 pid:28942 ppid: 21500 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
wait_for_unix_gc+0x14e/0x210 net/unix/garbage.c:201
unix_stream_sendmsg+0xc3/0x1070 net/unix/af_unix.c:2035
sock_sendmsg_nosec net/socket.c:704 [inline]
__sock_sendmsg net/socket.c:716 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2431
___sys_sendmsg+0x252/0x2e0 net/socket.c:2485
__sys_sendmsg net/socket.c:2514 [inline]
__do_sys_sendmsg net/socket.c:2523 [inline]
__se_sys_sendmsg+0x19a/0x260 net/socket.c:2521
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+0x61/0xcb
RIP: 0033:0x7f6cc720fda9
RSP: 002b:00007f6cc576f0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f6cc733e050 RCX: 00007f6cc720fda9
RDX: 0000000000040810 RSI: 0000000020000280 RDI: 0000000000000004
RBP: 00007f6cc725c47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f6cc733e050 R15: 00007fff1ea859d8
</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
5 locks held by kworker/u4:4/1233:
2 locks held by getty/3258:
#0: ffff88807e80a098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900024b32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
1 lock held by syz-executor.1/28881:
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.150-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/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 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 1233 Comm: kworker/u4:4 Not tainted 5.15.150-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: bat_events batadv_nc_worker
RIP: 0010:rcu_preempt_read_exit kernel/rcu/tree_plugin.h:380 [inline]
RIP: 0010:__rcu_read_unlock+0x2f/0x100 kernel/rcu/tree_plugin.h:419
Code: 41 55 41 54 53 49 bc 00 00 00 00 00 fc ff df 65 4c 8b 35 b4 cd 96 7e 4d 8d ae 3c 04 00 00 4c 89 eb 48 c1 eb 03 42 0f b6 04 23 <84> c0 75 61 41 8b 6d 00 ff cd 42 0f b6 04 23 84 c0 75 69 41 89 6d
RSP: 0018:ffffc90004fffbc0 EFLAGS: 00000a07
RAX: 0000000000000000 RBX: 1ffff11003ae7087 RCX: ffff88801d738000
RDX: 0000000000000000 RSI: ffffffff8ad88ea0 RDI: ffffffff8ad88e60
RBP: 0000000000000001 R08: ffffffff89f8f095 R09: fffffbfff1f79e19
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88801d73843c R14: ffff88801d738000 R15: ffff8880a044ad80
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000559ca06fc000 CR3: 000000001dc57000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
rcu_read_unlock include/linux/rcupdate.h:728 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:416 [inline]
batadv_nc_worker+0x234/0x5b0 net/batman-adv/network-coding.c:723
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: 80efc6265290 Linux 5.15.150
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14eb1c6a180000
kernel config: https://syzkaller.appspot.com/x/.config?x=928a06454760df60
dashboard link: https://syzkaller.appspot.com/bug?extid=81e4eaace743ea8b0379
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/178c37e05837/disk-80efc626.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c9672d0d3f85/vmlinux-80efc626.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3e859ffa360e/bzImage-80efc626.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+81e4ea...@syzkaller.appspotmail.com
INFO: task syz-executor.3:28905 blocked for more than 143 seconds.
Not tainted 5.15.150-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:27520 pid:28905 ppid: 20563 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
wait_for_unix_gc+0x14e/0x210 net/unix/garbage.c:201
unix_stream_sendmsg+0xc3/0x1070 net/unix/af_unix.c:2035
sock_sendmsg_nosec net/socket.c:704 [inline]
__sock_sendmsg net/socket.c:716 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2431
___sys_sendmsg+0x252/0x2e0 net/socket.c:2485
__sys_sendmsg net/socket.c:2514 [inline]
__do_sys_sendmsg net/socket.c:2523 [inline]
__se_sys_sendmsg+0x19a/0x260 net/socket.c:2521
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+0x61/0xcb
RIP: 0033:0x7f54b4a51da9
RSP: 002b:00007f54b2fd20c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f54b4b7ff80 RCX: 00007f54b4a51da9
RDX: 0000000020000001 RSI: 00000000200002c0 RDI: 0000000000000003
RBP: 00007f54b4a9e47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f54b4b7ff80 R15: 00007fff3fd33958
</TASK>
INFO: task syz-executor.0:28920 blocked for more than 143 seconds.
Not tainted 5.15.150-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:27712 pid:28920 ppid: 21633 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
wait_for_unix_gc+0x14e/0x210 net/unix/garbage.c:201
unix_stream_sendmsg+0xc3/0x1070 net/unix/af_unix.c:2035
sock_sendmsg_nosec net/socket.c:704 [inline]
__sock_sendmsg net/socket.c:716 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2431
___sys_sendmsg+0x252/0x2e0 net/socket.c:2485
__sys_sendmsg net/socket.c:2514 [inline]
__do_sys_sendmsg net/socket.c:2523 [inline]
__se_sys_sendmsg+0x19a/0x260 net/socket.c:2521
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+0x61/0xcb
RIP: 0033:0x7f8462d12da9
RSP: 002b:00007f84612930c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f8462e40f80 RCX: 00007f8462d12da9
RDX: 0000000020000001 RSI: 00000000200002c0 RDI: 0000000000000003
RBP: 00007f8462d5f47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f8462e40f80 R15: 00007ffc5a3c9898
</TASK>
INFO: task syz-executor.2:28942 blocked for more than 144 seconds.
Not tainted 5.15.150-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:27776 pid:28942 ppid: 21500 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
wait_for_unix_gc+0x14e/0x210 net/unix/garbage.c:201
unix_stream_sendmsg+0xc3/0x1070 net/unix/af_unix.c:2035
sock_sendmsg_nosec net/socket.c:704 [inline]
__sock_sendmsg net/socket.c:716 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2431
___sys_sendmsg+0x252/0x2e0 net/socket.c:2485
__sys_sendmsg net/socket.c:2514 [inline]
__do_sys_sendmsg net/socket.c:2523 [inline]
__se_sys_sendmsg+0x19a/0x260 net/socket.c:2521
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+0x61/0xcb
RIP: 0033:0x7f6cc720fda9
RSP: 002b:00007f6cc576f0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f6cc733e050 RCX: 00007f6cc720fda9
RDX: 0000000000040810 RSI: 0000000020000280 RDI: 0000000000000004
RBP: 00007f6cc725c47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f6cc733e050 R15: 00007fff1ea859d8
</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
5 locks held by kworker/u4:4/1233:
2 locks held by getty/3258:
#0: ffff88807e80a098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900024b32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
1 lock held by syz-executor.1/28881:
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.150-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/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 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 1233 Comm: kworker/u4:4 Not tainted 5.15.150-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: bat_events batadv_nc_worker
RIP: 0010:rcu_preempt_read_exit kernel/rcu/tree_plugin.h:380 [inline]
RIP: 0010:__rcu_read_unlock+0x2f/0x100 kernel/rcu/tree_plugin.h:419
Code: 41 55 41 54 53 49 bc 00 00 00 00 00 fc ff df 65 4c 8b 35 b4 cd 96 7e 4d 8d ae 3c 04 00 00 4c 89 eb 48 c1 eb 03 42 0f b6 04 23 <84> c0 75 61 41 8b 6d 00 ff cd 42 0f b6 04 23 84 c0 75 69 41 89 6d
RSP: 0018:ffffc90004fffbc0 EFLAGS: 00000a07
RAX: 0000000000000000 RBX: 1ffff11003ae7087 RCX: ffff88801d738000
RDX: 0000000000000000 RSI: ffffffff8ad88ea0 RDI: ffffffff8ad88e60
RBP: 0000000000000001 R08: ffffffff89f8f095 R09: fffffbfff1f79e19
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88801d73843c R14: ffff88801d738000 R15: ffff8880a044ad80
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000559ca06fc000 CR3: 000000001dc57000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
rcu_read_unlock include/linux/rcupdate.h:728 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:416 [inline]
batadv_nc_worker+0x234/0x5b0 net/batman-adv/network-coding.c:723
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
Mar 2, 2024, 10:41:16 PMMar 2
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: a3eb3a74aa8c Linux 6.1.80
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=111b9306180000
kernel config: https://syzkaller.appspot.com/x/.config?x=36414e87ed688c3e
dashboard link: https://syzkaller.appspot.com/bug?extid=8429d293417cb79835a3
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11844096180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=142070e4180000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7b860e20bba4/disk-a3eb3a74.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/99963b158c4f/vmlinux-a3eb3a74.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9118951594af/bzImage-a3eb3a74.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
INFO: task syz-executor122:11992 blocked for more than 143 seconds.
Not tainted 6.1.80-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor122 state:D stack:27208 pid:11992 ppid:3569 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
wait_for_unix_gc+0x14c/0x210 net/unix/garbage.c:201
unix_stream_sendmsg+0xc3/0x1070 net/unix/af_unix.c:2167
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg net/socket.c:730 [inline]
____sys_sendmsg+0x5a5/0x8f0 net/socket.c:2514
___sys_sendmsg net/socket.c:2568 [inline]
__sys_sendmsg+0x2a9/0x390 net/socket.c:2597
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fecb7b4d7a9
RSP: 002b:00007ffc61e733e8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fecb7b4d7a9
RDX: 0000000000000041 RSI: 0000000020001480 RDI: 0000000000000003
RBP: 0000000000084ebf R08: 00007fecb7b8f09e R09: 00007fecb7b8f09e
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc61e7349c
R13: 431bde82d7b634db R14: 00007ffc61e734c0 R15: 00007ffc61e734a0
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
Showing all locks held in the system:
#0: ffffffff8d12aa90 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d12b290 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffffffff8d12a8c0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:319 [inline]
#0: ffffffff8d12a8c0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:760 [inline]
#0: ffffffff8d12a8c0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6494
2 locks held by kworker/u4:3/46:
#0: ffff888012479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90000b77d20 ((work_completion)(&(&kfence_timer)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
1 lock held by dhcpcd/3216:
2 locks held by getty/3302:
#0: ffff88814b997098 (&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:2188
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.80-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/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+0x4e1/0x560 lib/nmi_backtrace.c:111
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
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+0xf88/0xfd0 kernel/hung_task.c:377
kthread+0x28d/0x320 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: 3216 Comm: dhcpcd Not tainted 6.1.80-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:unix_gc+0x1082/0x13e0
Code: a0 f8 e9 13 ff ff ff e8 2c cf 48 f8 eb 05 e8 25 cf 48 f8 48 8b 1d 4e 68 f7 04 49 c7 c7 40 18 39 8e 4c 39 fb 0f 84 aa 00 00 00 <48> 89 d8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df 80 3c 08 00 74
RSP: 0018:ffffc900034dfa60 EFLAGS: 00000293
RAX: ffffffff8941b09d RBX: ffff88807e71f650 RCX: ffff888029260000
RDX: 0000000000000000 RSI: ffffffff8aebed40 RDI: ffffffff8b3d1140
RBP: ffffc900034dfbd0 R08: dffffc0000000000 R09: fffffbfff2092058
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807e71f650
R13: 1ffff1100fce3eee R14: 0000000000000000 R15: ffffffff8e391840
FS: 00007f7ff886a740(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001480 CR3: 0000000021ba3000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
unix_release_sock+0xab8/0xcf0 net/unix/af_unix.c:669
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
unix_release+0x88/0xc0 net/unix/af_unix.c:1039
__sock_release net/socket.c:654 [inline]
sock_close+0xcd/0x230 net/socket.c:1400
__fput+0x3b7/0x890 fs/file_table.c:320
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+0xde/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:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7ff89350a8
Code: 48 8b 05 83 9d 0d 00 64 c7 00 16 00 00 00 83 c8 ff 48 83 c4 20 5b c3 64 8b 04 25 18 00 00 00 85 c0 75 20 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 76 5b 48 8b 15 51 9d 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffe923cbed8 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00007f7ff89350a8
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000017
RBP: 00007ffe923ec288 R08: 0000000000000007 R09: 247827cf7e7347b2
R10: 0000000000004000 R11: 0000000000000246 R12: 000055f6168fe4f0
R13: 00007ffe923dc0c8 R14: 0000000000000148 R15: 0000000000000004
</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 syzbot to run the reproducer, reply with:
---
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
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
Reply all
Reply to author
Forward
0 new messages