[v6.1] INFO: task hung in packet_mc_add

0 views
Skip to first unread message

syzbot

unread,
Mar 17, 2023, 8:24:43 PM3/17/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 7eaef76fbc46 Linux 6.1.20
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17bb5126c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=28c36fe4d02f8c88
dashboard link: https://syzkaller.appspot.com/bug?extid=64e3650203822c4210c1
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/610a00ba4375/disk-7eaef76f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/57c1310f9a30/vmlinux-7eaef76f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/81999f717d3b/bzImage-7eaef76f.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+64e365...@syzkaller.appspotmail.com

INFO: task syz-executor.0:23171 blocked for more than 143 seconds.
Not tainted 6.1.20-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:28360 pid:23171 ppid:3667 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5238 [inline]
__schedule+0x1391/0x4390 kernel/sched/core.c:6551
schedule+0xbf/0x180 kernel/sched/core.c:6627
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6686
__mutex_lock_common+0xe2b/0x2520 kernel/locking/mutex.c:679
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
packet_mc_add+0x28/0x930 net/packet/af_packet.c:3656
packet_setsockopt+0xe55/0x1780 net/packet/af_packet.c:3778
__sys_setsockopt+0x57e/0xa00 net/socket.c:2252
__do_sys_setsockopt net/socket.c:2263 [inline]
__se_sys_setsockopt net/socket.c:2260 [inline]
__x64_sys_setsockopt+0xb1/0xc0 net/socket.c:2260
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:0x7f7d4208c0f9
RSP: 002b:00007f7d42e63168 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007f7d421ac050 RCX: 00007f7d4208c0f9
RDX: 0000000000000001 RSI: 0000000000000107 RDI: 0000000000000003
RBP: 00007f7d420e7b39 R08: 0000000000000010 R09: 0000000000000000
R10: 0000000020000280 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffeca7f7def R14: 00007f7d42e63300 R15: 0000000000022000
</TASK>
INFO: task syz-executor.0:23172 blocked for more than 143 seconds.
Not tainted 6.1.20-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:28952 pid:23172 ppid:3667 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5238 [inline]
__schedule+0x1391/0x4390 kernel/sched/core.c:6551
schedule+0xbf/0x180 kernel/sched/core.c:6627
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6686
__mutex_lock_common+0xe2b/0x2520 kernel/locking/mutex.c:679
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
packet_mc_add+0x28/0x930 net/packet/af_packet.c:3656
packet_setsockopt+0xe55/0x1780 net/packet/af_packet.c:3778
__sys_setsockopt+0x57e/0xa00 net/socket.c:2252
__do_sys_setsockopt net/socket.c:2263 [inline]
__se_sys_setsockopt net/socket.c:2260 [inline]
__x64_sys_setsockopt+0xb1/0xc0 net/socket.c:2260
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:0x7f7d4208c0f9
RSP: 002b:00007f7d42e42168 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007f7d421ac120 RCX: 00007f7d4208c0f9
RDX: 0000000000000001 RSI: 0000000000000107 RDI: 0000000000000003
RBP: 00007f7d420e7b39 R08: 0000000000000010 R09: 0000000000000000
R10: 0000000020000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffeca7f7def R14: 00007f7d42e42300 R15: 0000000000022000
</TASK>
INFO: task syz-executor.1:23186 blocked for more than 144 seconds.
Not tainted 6.1.20-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:27288 pid:23186 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5238 [inline]
__schedule+0x1391/0x4390 kernel/sched/core.c:6551
schedule+0xbf/0x180 kernel/sched/core.c:6627
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6686
__mutex_lock_common+0xe2b/0x2520 kernel/locking/mutex.c:679
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
rtnl_lock net/core/rtnetlink.c:74 [inline]
rtnetlink_rcv_msg+0x720/0xf00 net/core/rtnetlink.c:6088
netlink_rcv_skb+0x1cd/0x410 net/netlink/af_netlink.c:2550
netlink_unicast_kernel net/netlink/af_netlink.c:1328 [inline]
netlink_unicast+0x7bf/0x990 net/netlink/af_netlink.c:1354
netlink_sendmsg+0xa26/0xd60 net/netlink/af_netlink.c:1931
sock_sendmsg_nosec net/socket.c:716 [inline]
sock_sendmsg net/socket.c:736 [inline]
__sys_sendto+0x471/0x5f0 net/socket.c:2117
__do_sys_sendto net/socket.c:2129 [inline]
__se_sys_sendto net/socket.c:2125 [inline]
__x64_sys_sendto+0xda/0xf0 net/socket.c:2125
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:0x7fe44623e12c
RSP: 002b:00007ffc45591b40 EFLAGS: 00000293 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffda RBX: 00007fe446ed4620 RCX: 00007fe44623e12c
RDX: 0000000000000028 RSI: 00007fe446ed4670 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007ffc45591b94 R09: 000000000000000c
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000
R13: 00007fe446ed4670 R14: 0000000000000003 R15: 0000000000000000
</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/3311:
#0: ffff888144f59098 (&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
3 locks held by kworker/0:5/11553:
#0: ffff88814ad1ed38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x77b/0x1380
#1: ffffc90005e8fd20 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7be/0x1380 kernel/workqueue.c:2264
#2: ffffffff8e090408 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x15/0x30 net/ipv6/addrconf.c:4629
2 locks held by kworker/u4:61/14486:
#0: ffff8880b9939dd8 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:537
#1: ffffffff8cf272a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:305
3 locks held by kworker/1:0/19625:
#0: ffff88814ad1ed38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x77b/0x1380
#1: ffffc900051ffd20 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7be/0x1380 kernel/workqueue.c:2264
#2: ffffffff8e090408 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x15/0x30 net/ipv6/addrconf.c:4629
3 locks held by syz-executor.1/23145:
1 lock held by syz-executor.0/23171:
#0: ffffffff8e090408 (rtnl_mutex){+.+.}-{3:3}, at: packet_mc_add+0x28/0x930 net/packet/af_packet.c:3656
1 lock held by syz-executor.0/23172:
#0: ffffffff8e090408 (rtnl_mutex){+.+.}-{3:3}, at: packet_mc_add+0x28/0x930 net/packet/af_packet.c:3656
1 lock held by syz-executor.1/23186:
#0: ffffffff8e090408 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8e090408 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x720/0xf00 net/core/rtnetlink.c:6088
1 lock held by syz-executor.1/23195:
#0: ffffffff8e090408 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8e090408 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x720/0xf00 net/core/rtnetlink.c:6088
1 lock held by syz-executor.1/23200:
#0: ffffffff8e090408 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8e090408 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x720/0xf00 net/core/rtnetlink.c:6088

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.20-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/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+0xff3/0x1040 kernel/hung_task.c:377
kthread+0x268/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: 23145 Comm: syz-executor.1 Not tainted 6.1.20-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:check_preemption_disabled+0x5c/0x110 lib/smp_processor_id.c:19
Code: 25 28 00 00 00 48 3b 44 24 08 0f 85 c7 00 00 00 89 d8 48 83 c4 10 5b 41 5c 41 5e 41 5f c3 48 c7 04 24 00 00 00 00 9c 8f 04 24 <f7> 04 24 00 02 00 00 74 c9 49 89 f6 49 89 ff 65 4c 8b 25 1d 07 78
RSP: 0018:ffffc900159fdd28 EFLAGS: 00000046
RAX: 0000000080000000 RBX: 0000000000000001 RCX: ffffffff91a64003
RDX: dffffc0000000000 RSI: ffffffff8aebe000 RDI: ffffffff8b3d2900
RBP: ffffc900159fde08 R08: ffffffff818358d5 R09: fffff94000161501
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888079240000
R13: 0000000000000001 R14: 4421295992ce8b8e R15: 1ffff92002b3fbb0
FS: 00007f162c1eb700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c002982000 CR3: 000000006b454000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lockdep_recursion_inc kernel/locking/lockdep.c:462 [inline]
lockdep_hardirqs_on_prepare+0x1f4/0x7a0 kernel/locking/lockdep.c:4321
trace_hardirqs_on+0x34/0x40 kernel/trace/trace_preemptirq.c:49
count_memcg_events include/linux/memcontrol.h:1061 [inline]
count_memcg_folio_events include/linux/memcontrol.h:1079 [inline]
shrink_folio_list+0x1b8f/0x9360 mm/vmscan.c:2061
evict_folios+0xb42/0x2810 mm/vmscan.c:5017
lru_gen_shrink_lruvec mm/vmscan.c:5201 [inline]
shrink_lruvec+0xdbf/0x4720 mm/vmscan.c:5896
</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.

syzbot

unread,
Jul 15, 2023, 8:24:44 PM7/15/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages