INFO: task hung in lock_sock_nested (3)

7 views
Skip to first unread message

syzbot

unread,
Jun 23, 2022, 6:52:22 PM6/23/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12d79d1ff00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=3afaac5a56f7a2935e5f
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+3afaac...@syzkaller.appspotmail.com

Bluetooth: hci2: command 0x0406 tx timeout
Bluetooth: hci1: command 0x0406 tx timeout
Bluetooth: hci5: command 0x0406 tx timeout
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
INFO: task syz-executor.4:11826 blocked for more than 140 seconds.
Not tainted 4.19.211-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.4 D30184 11826 8168 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
__lock_sock+0x13d/0x260 net/core/sock.c:2338
lock_sock_nested+0xf1/0x110 net/core/sock.c:2886
lock_sock include/net/sock.h:1512 [inline]
tipc_setsockopt+0x493/0x9f0 net/tipc/socket.c:2920
__sys_setsockopt+0x14d/0x240 net/socket.c:2013
__do_sys_setsockopt net/socket.c:2024 [inline]
__se_sys_setsockopt net/socket.c:2021 [inline]
__x64_sys_setsockopt+0xba/0x150 net/socket.c:2021
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7ffa6aedb109
Code: Bad RIP value.
RSP: 002b:00007ffa6982f168 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007ffa6afee030 RCX: 00007ffa6aedb109
RDX: 0000000000000088 RSI: 000000000000010f RDI: 0000000000000005
RBP: 00007ffa6af3505d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe4d53b83f R14: 00007ffa6982f300 R15: 0000000000022000

Showing all locks held in the system:
2 locks held by kworker/u4:3/285:
#0: 00000000c71c8733 (&rq->lock){-.-.}, at: rq_lock kernel/sched/sched.h:1826 [inline]
#0: 00000000c71c8733 (&rq->lock){-.-.}, at: __schedule+0x1f9/0x2040 kernel/sched/core.c:3455
#1: 0000000007f56c17 (rcu_read_lock){....}, at: trace_sched_stat_runtime include/trace/events/sched.h:428 [inline]
#1: 0000000007f56c17 (rcu_read_lock){....}, at: update_curr+0x2c3/0x870 kernel/sched/fair.c:857
1 lock held by khungtaskd/1568:
#0: 0000000007f56c17 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by systemd-journal/4691:
1 lock held by in:imklog/7833:
#0: 000000002b41fb23 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
3 locks held by syz-executor.4/11807:

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

NMI backtrace for cpu 1
CPU: 1 PID: 1568 Comm: khungtaskd Not tainted 4.19.211-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 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4691 Comm: systemd-journal Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__read_once_size include/linux/compiler.h:263 [inline]
RIP: 0010:check_kcov_mode kernel/kcov.c:69 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x1c/0x50 kernel/kcov.c:101
Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 90 48 8b 34 24 65 48 8b 04 25 c0 df 01 00 65 8b 15 cc 59 9f 7e 81 e2 00 01 1f 00 75 2b <8b> 90 60 13 00 00 83 fa 02 75 20 48 8b 88 68 13 00 00 8b 80 64 13
RSP: 0018:ffff8880a0e17700 EFLAGS: 00000046
RAX: ffff8880a0e0e540 RBX: 0000000000000000 RCX: ffffffff8167ada7
RDX: 0000000000000000 RSI: ffffffff8167adb0 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888044daf500
R13: ffff8880a0e17770 R14: ffff88823b33a540 R15: 0000000000000286
FS: 00007fb06a69b8c0(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb067adb008 CR3: 00000000a138d000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
trace_hardirqs_off+0x50/0x200 kernel/trace/trace_preemptirq.c:40
qlink_free mm/kasan/quarantine.c:145 [inline]
qlist_free_all+0x67/0x140 mm/kasan/quarantine.c:166
quarantine_reduce+0x1a9/0x230 mm/kasan/quarantine.c:259
kasan_kmalloc+0xa2/0x160 mm/kasan/kasan.c:538
slab_post_alloc_hook mm/slab.h:445 [inline]
slab_alloc mm/slab.c:3397 [inline]
kmem_cache_alloc_trace+0x11a/0x380 mm/slab.c:3623
kmalloc include/linux/slab.h:515 [inline]
kzalloc include/linux/slab.h:709 [inline]
aa_alloc_file_ctx security/apparmor/include/file.h:60 [inline]
apparmor_file_alloc_security+0x394/0xad0 security/apparmor/lsm.c:438
security_file_alloc+0x40/0x90 security/security.c:880
__alloc_file+0xd8/0x340 fs/file_table.c:105
alloc_empty_file+0x6d/0x170 fs/file_table.c:150
path_openat+0xe9/0x2df0 fs/namei.c:3526
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fb069c2a840
Code: 73 01 c3 48 8b 0d 68 77 20 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d 89 bb 20 00 00 75 10 b8 02 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 1e f6 ff ff 48 89 04 24
RSP: 002b:00007ffd115bdfd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007ffd115be2e0 RCX: 00007fb069c2a840
RDX: 00000000000001a0 RSI: 0000000000080042 RDI: 00005577979fc310
RBP: 000000000000000d R08: 00007fb069c14cb8 R09: 00000000ffffffff
R10: 0000000000000069 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00005577979f0040 R14: 00007ffd115be2a0 R15: 00005577979fd740
----------------
Code disassembly (best guess):
0: 90 nop
1: 90 nop
2: 90 nop
3: 90 nop
4: 90 nop
5: 90 nop
6: 90 nop
7: 90 nop
8: 90 nop
9: 90 nop
a: 90 nop
b: 90 nop
c: 90 nop
d: 90 nop
e: 48 8b 34 24 mov (%rsp),%rsi
12: 65 48 8b 04 25 c0 df mov %gs:0x1dfc0,%rax
19: 01 00
1b: 65 8b 15 cc 59 9f 7e mov %gs:0x7e9f59cc(%rip),%edx # 0x7e9f59ee
22: 81 e2 00 01 1f 00 and $0x1f0100,%edx
28: 75 2b jne 0x55
* 2a: 8b 90 60 13 00 00 mov 0x1360(%rax),%edx <-- trapping instruction
30: 83 fa 02 cmp $0x2,%edx
33: 75 20 jne 0x55
35: 48 8b 88 68 13 00 00 mov 0x1368(%rax),%rcx
3c: 8b .byte 0x8b
3d: 80 .byte 0x80
3e: 64 fs
3f: 13 .byte 0x13


---
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.
Reply all
Reply to author
Forward
0 new messages