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=1054f4cdf00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link:
https://syzkaller.appspot.com/bug?extid=f7ebd91fee6754d99dd3
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+f7ebd9...@syzkaller.appspotmail.com
ieee802154 phy1 wpan1: encryption failed: -22
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
INFO: task syz-executor.1:997 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.1 D29952 997 31528 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:1016 [inline]
__mutex_lock+0x5f0/0x1190 kernel/locking/mutex.c:1078
mutex_lock_double kernel/events/core.c:10470 [inline]
__perf_event_ctx_lock_double kernel/events/core.c:10529 [inline]
__do_sys_perf_event_open kernel/events/core.c:10784 [inline]
__se_sys_perf_event_open+0x1863/0x2720 kernel/events/core.c:10549
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f0e3aec3109
Code: Bad RIP value.
RSP: 002b:00007f0e39817168 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 00007f0e3afd6030 RCX: 00007f0e3aec3109
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000020000000
RBP: 00007f0e3af1d08d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000004 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc8398419f R14: 00007f0e39817300 R15: 0000000000022000
Showing all locks held in the system:
1 lock held by khungtaskd/1570:
#0: 00000000b3f24cf6 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
no locks held by in:imklog/7777.
1 lock held by syz-executor.1/995:
#0: 000000006ca1bef4 (&cpuctx_mutex){+.+.}, at: perf_event_ctx_lock_nested+0x237/0x430 kernel/events/core.c:1283
2 locks held by syz-executor.1/997:
#0: 000000006ca1bef4 (&cpuctx_mutex){+.+.}, at: mutex_lock_double kernel/events/core.c:10469 [inline]
#0: 000000006ca1bef4 (&cpuctx_mutex){+.+.}, at: __perf_event_ctx_lock_double kernel/events/core.c:10529 [inline]
#0: 000000006ca1bef4 (&cpuctx_mutex){+.+.}, at: __do_sys_perf_event_open kernel/events/core.c:10784 [inline]
#0: 000000006ca1bef4 (&cpuctx_mutex){+.+.}, at: __se_sys_perf_event_open+0x1856/0x2720 kernel/events/core.c:10549
#1: 000000006ca1bef4 (&cpuctx_mutex/1){+.+.}, at: mutex_lock_double kernel/events/core.c:10470 [inline]
#1: 000000006ca1bef4 (&cpuctx_mutex/1){+.+.}, at: __perf_event_ctx_lock_double kernel/events/core.c:10529 [inline]
#1: 000000006ca1bef4 (&cpuctx_mutex/1){+.+.}, at: __do_sys_perf_event_open kernel/events/core.c:10784 [inline]
#1: 000000006ca1bef4 (&cpuctx_mutex/1){+.+.}, at: __se_sys_perf_event_open+0x1863/0x2720 kernel/events/core.c:10549
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 1570 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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4696 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:preempt_count arch/x86/include/asm/preempt.h:23 [inline]
RIP: 0010:check_kcov_mode kernel/kcov.c:67 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0xd/0x50 kernel/kcov.c:101
Code: ff 4c 89 ef e8 04 dd 35 00 e9 23 fe ff ff 90 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
RSP: 0018:ffff8880a0967a28 EFLAGS: 00000282
RAX: ffff8880a095a680 RBX: dffffc0000000000 RCX: ffffffff8162b98c
RDX: ffff8880a0967ac0 RSI: ffffffff816c36e5 RDI: ffff8880a0967b00
RBP: ffff8880a0967b00 R08: 0000000000000000 R09: 000000007fff0000
R10: 0000000000000004 R11: 0000000000000000 R12: ffffffff886fb460
R13: ffffed101412cf62 R14: ffffc90001a93038 R15: 000000007fff0000
FS: 00007f99c33f28c0(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f99c0b46000 CR3: 00000000a0f18000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
___bpf_prog_run+0x45/0x4e80 kernel/bpf/core.c:1065
----------------
Code disassembly (best guess):
0: ff 4c 89 ef decl -0x11(%rcx,%rcx,4)
4: e8 04 dd 35 00 callq 0x35dd0d
9: e9 23 fe ff ff jmpq 0xfffffe31
e: 90 nop
f: 90 nop
10: 90 nop
11: 90 nop
12: 90 nop
13: 90 nop
14: 90 nop
15: 90 nop
16: 90 nop
17: 90 nop
18: 90 nop
19: 90 nop
1a: 90 nop
1b: 90 nop
1c: 90 nop
1d: 48 8b 34 24 mov (%rsp),%rsi
21: 65 48 8b 04 25 c0 df mov %gs:0x1dfc0,%rax
28: 01 00
* 2a: 65 8b 15 cc 59 9f 7e mov %gs:0x7e9f59cc(%rip),%edx # 0x7e9f59fd <-- trapping instruction
31: 81 e2 00 01 1f 00 and $0x1f0100,%edx
37: 75 2b jne 0x64
39: 8b 90 60 13 00 00 mov 0x1360(%rax),%edx
3f: 83 .byte 0x83
---
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.