INFO: task hung in rtnetlink_rcv_msg (2)

6 views
Skip to first unread message

syzbot

unread,
Jul 23, 2021, 12:37:18 AM7/23/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 4938296e03bd Linux 4.19.198
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=128a2cb2300000
kernel config: https://syzkaller.appspot.com/x/.config?x=9013c716691ad1fe
dashboard link: https://syzkaller.appspot.com/bug?extid=71f8709a75e6edb269a0
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Unfortunately, I don't have any reproducer for this issue yet.

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

ieee802154 phy1 wpan1: encryption failed: -22
Bluetooth: hci5: command 0x0406 tx timeout
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
Bluetooth: hci3: command 0x0406 tx timeout
INFO: task syz-executor.3:11006 blocked for more than 140 seconds.
Not tainted 4.19.198-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.3 D28536 11006 1 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
__mutex_lock_common kernel/locking/mutex.c:1015 [inline]
__mutex_lock+0x604/0x1200 kernel/locking/mutex.c:1083
rtnl_lock net/core/rtnetlink.c:77 [inline]
rtnetlink_rcv_msg+0x3fe/0xb80 net/core/rtnetlink.c:4779
netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2457
netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]
netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1346
netlink_sendmsg+0x6bb/0xc40 net/netlink/af_netlink.c:1911
sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:661
__sys_sendto+0x21a/0x320 net/socket.c:1897
__do_sys_sendto net/socket.c:1909 [inline]
__se_sys_sendto net/socket.c:1905 [inline]
__x64_sys_sendto+0xdd/0x1b0 net/socket.c:1905
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x41957c
Code: Bad RIP value.
RSP: 002b:00007ffceb505110 EFLAGS: 00000293 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffda RBX: 00000000014a4320 RCX: 000000000041957c
RDX: 0000000000000028 RSI: 00000000014a4370 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007ffceb505164 R09: 000000000000000c
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000
R13: 00000000014a4370 R14: 0000000000000003 R15: 0000000000000000

Showing all locks held in the system:
3 locks held by kworker/0:1/14:
#0: 0000000004b2855b ((wq_completion)"%s"("ipv6_addrconf")){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
#1: 000000003ae4e037 ((addr_chk_work).work){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
#2: 00000000f3c4df5f (rtnl_mutex){+.+.}, at: addrconf_verify_work+0xa/0x20 net/ipv6/addrconf.c:4476
1 lock held by khungtaskd/1571:
#0: 0000000021861109 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by in:imklog/7809:
#0: 00000000d9636613 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
4 locks held by kworker/u4:5/9763:
3 locks held by kworker/u4:7/22135:
#0: 0000000035652bba (&rq->lock){-.-.}, at: rq_lock kernel/sched/sched.h:1824 [inline]
#0: 0000000035652bba (&rq->lock){-.-.}, at: __schedule+0x1f9/0x2040 kernel/sched/core.c:3455
#1: 0000000021861109 (rcu_read_lock){....}, at: trace_sched_stat_runtime include/trace/events/sched.h:428 [inline]
#1: 0000000021861109 (rcu_read_lock){....}, at: update_curr+0x2c3/0x870 kernel/sched/fair.c:857
#2: 00000000fb97f07f (&wdev->mtx){+.+.}, at: sdata_lock net/mac80211/ieee80211_i.h:977 [inline]
#2: 00000000fb97f07f (&wdev->mtx){+.+.}, at: ieee80211_ibss_work+0x85/0xe10 net/mac80211/ibss.c:1675
1 lock held by syz-executor.3/11006:
#0: 00000000f3c4df5f (rtnl_mutex){+.+.}, at: rtnl_lock net/core/rtnetlink.c:77 [inline]
#0: 00000000f3c4df5f (rtnl_mutex){+.+.}, at: rtnetlink_rcv_msg+0x3fe/0xb80 net/core/rtnetlink.c:4779

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

NMI backtrace for cpu 0
CPU: 0 PID: 1571 Comm: khungtaskd Not tainted 4.19.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1a6/0x1f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
watchdog+0x991/0xe60 kernel/hung_task.c:287
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4677 Comm: systemd-journal Not tainted 4.19.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:777 [inline]
RIP: 0010:debug_check_no_obj_freed+0x1ce/0x490 lib/debugobjects.c:817
Code: 00 00 00 ad de 4d 89 60 08 4c 89 c7 49 89 00 e8 a8 d6 ff ff 09 c3 4d 85 f6 74 2c 4d 89 f0 4c 89 c0 48 c1 e8 03 42 80 3c 38 00 <0f> 84 23 ff ff ff 4c 89 c7 4c 89 44 24 38 e8 5f fb 20 fe 4c 8b 44
RSP: 0018:ffff8880a1a47da0 EFLAGS: 00000046
RAX: 1ffff110086857c7 RBX: 0000000000000000 RCX: ffffffff814bdcab
RDX: 1ffffffff1a8371b RSI: 0000000000000004 RDI: ffff88809930aec0
RBP: 0000000000000006 R08: ffff88804342be38 R09: ffff888044414b40
R10: ffffffff8d41b8cb R11: 0000000000000000 R12: dead000000000200
R13: ffff888098d78d00 R14: ffff88804342be38 R15: dffffc0000000000
FS: 00007f7bc7dda8c0(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c02359c480 CR3: 00000000a1a8f000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
kmem_cache_free+0xff/0x260 mm/slab.c:3764
__put_cred+0x1de/0x250 kernel/cred.c:151
put_cred include/linux/cred.h:276 [inline]
do_faccessat+0x64e/0x7a0 fs/open.c:438
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f7bc70959c7
Code: 83 c4 08 48 3d 01 f0 ff ff 73 01 c3 48 8b 0d c8 d4 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 b8 15 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a1 d4 2b 00 f7 d8 64 89 01 48
RSP: 002b:00007ffe054ca158 EFLAGS: 00000246 ORIG_RAX: 0000000000000015
RAX: ffffffffffffffda RBX: 00007ffe054cd180 RCX: 00007f7bc70959c7
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00005563d35ec9a3
RBP: 00007ffe054ca2a0 R08: 00005563d35e23e5 R09: 0000000000000018
R10: 0000000000000069 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00005563d47e78a0 R15: 00007ffe054ca790


---
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,
May 18, 2022, 7:30:20 AM5/18/22
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