[v6.1] INFO: rcu detected stall in syscall_enter_from_user_mode
0 views
Skip to first unread message
syzbot
Jul 5, 2023, 2:45:58 AM7/5/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 0f4ac6b4c5f0 Linux 6.1.37
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16a5d63ca80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b078ded3c2c9e539
dashboard link: https://syzkaller.appspot.com/bug?extid=00eb717e1ccc483c54e7
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/07d69feeab55/disk-0f4ac6b4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9668616ecc4b/vmlinux-0f4ac6b4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/bab83d45dde7/bzImage-0f4ac6b4.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+00eb71...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 1-...!: (0 ticks this GP) idle=924c/1/0x4000000000000000 softirq=108658/108658 fqs=0
(detected by 0, t=10502 jiffies, g=154257, q=82 ncpus=2)
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 2171 Comm: syz-executor.1 Not tainted 6.1.37-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:hlock_class kernel/locking/lockdep.c:228 [inline]
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4731 [inline]
RIP: 0010:__lock_acquire+0x552/0x1f80 kernel/locking/lockdep.c:5006
Code: 41 8b 1e 81 e3 ff 1f 00 00 48 89 d8 48 c1 e8 06 48 8d 3c c5 20 c2 28 90 be 08 00 00 00 e8 16 65 76 00 48 0f a3 1d 9e e4 be 0e <73> 1f 48 8d 04 5b 48 c1 e0 06 48 8d 98 20 21 f8 8f 48 ba 00 00 00
RSP: 0018:ffffc900001e0a00 EFLAGS: 00000057
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffffffff8169dd7a
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff9028c220
RBP: 0000000000000002 R08: dffffc0000000000 R09: fffffbfff2051845
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88808586c658
R13: ffff88808586bb80 R14: ffff88808586c6a8 R15: 1ffff11010b0d8d5
FS: 00007fc49816d700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30821000 CR3: 000000007866b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
debug_object_deactivate+0x61/0x3f0 lib/debugobjects.c:763
debug_hrtimer_deactivate kernel/time/hrtimer.c:425 [inline]
debug_deactivate+0x1d/0x280 kernel/time/hrtimer.c:481
__run_hrtimer kernel/time/hrtimer.c:1653 [inline]
__hrtimer_run_queues+0x334/0xe50 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:__syscall_enter_from_user_work kernel/entry/common.c:91 [inline]
RIP: 0010:syscall_enter_from_user_mode+0x37/0x220 kernel/entry/common.c:112
Code: 49 89 fe 48 8b 7c 24 30 e8 f6 fa ff ff 0f 1f 44 00 00 0f 1f 44 00 00 e8 57 73 0c f7 e8 d2 71 0c f7 fb 65 4c 8b 3d c9 53 7e 75 <49> 8b 6f 08 40 f6 c5 3f 0f 84 b5 00 00 00 40 f6 c5 20 74 17 4c 89
RSP: 0018:ffffc9000aa3fef8 EFLAGS: 00000282
RAX: 3229529ed05bbe00 RBX: 00000000000000ca RCX: ffffffff91a84103
RDX: dffffc0000000000 RSI: ffffffff8aebd220 RDI: ffffffff8b3ccd60
RBP: ffffc9000aa3ff48 R08: dffffc0000000000 R09: fffffbfff1ca663e
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: ffffc9000aa3ff58 R15: ffff88808586bb80
do_syscall_64+0x1e/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc49748c389
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc49816d218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007fc4975ac058 RCX: 00007fc49748c389
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fc4975ac058
RBP: 00007fc4975ac050 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fc4975ac05c
R13: 00007fffdf0718df R14: 00007fc49816d300 R15: 0000000000022000
</TASK>
rcu: rcu_preempt kthread timer wakeup didn't happen for 10501 jiffies! g154257 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: Possible timer handling issue on cpu=1 timer-softirq=129375
rcu: rcu_preempt kthread starved for 10502 jiffies! g154257 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:I stack:25432 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1935
rcu_gp_fqs_loop+0x2c2/0x1010 kernel/rcu/tree.c:1661
rcu_gp_kthread+0xa3/0x3a0 kernel/rcu/tree.c:1860
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 2171 Comm: syz-executor.1 Not tainted 6.1.37-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:101 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:128 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:159 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline]
RIP: 0010:kasan_check_range+0x5f/0x290 mm/kasan/generic.c:189
Code: eb 03 49 b8 00 00 00 00 00 fc ff df 4e 8d 0c 03 4c 8d 54 37 ff 49 c1 ea 03 49 bb 01 00 00 00 00 fc ff df 4f 8d 34 1a 4c 89 f5 <4c> 29 cd 48 83 fd 10 7f 26 48 85 ed 0f 84 3a 01 00 00 49 f7 d2 49
RSP: 0018:ffffc900001e09d8 EFLAGS: 00000803
RAX: 0000000000000001 RBX: 1ffffffff1ca663d RCX: ffffffff8169d23b
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8e5331e8
RBP: fffffbfff1ca663e R08: dffffc0000000000 R09: fffffbfff1ca663d
R10: 1ffffffff1ca663d R11: dffffc0000000001 R12: 1ffff9200003c148
R13: dffffc0000000000 R14: fffffbfff1ca663e R15: dffffc0000000000
FS: 00007fc49816d700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30821000 CR3: 000000007866b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
instrument_atomic_read include/linux/instrumented.h:72 [inline]
_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
cpumask_test_cpu include/linux/cpumask.h:444 [inline]
cpu_online include/linux/cpumask.h:1030 [inline]
trace_lock_acquire include/trace/events/lock.h:24 [inline]
lock_acquire+0xeb/0x5a0 kernel/locking/lockdep.c:5640
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
debug_object_activate+0x16b/0x860 lib/debugobjects.c:697
debug_hrtimer_activate kernel/time/hrtimer.c:420 [inline]
debug_activate kernel/time/hrtimer.c:475 [inline]
enqueue_hrtimer+0x30/0x390 kernel/time/hrtimer.c:1084
__run_hrtimer kernel/time/hrtimer.c:1702 [inline]
__hrtimer_run_queues+0x728/0xe50 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:__syscall_enter_from_user_work kernel/entry/common.c:91 [inline]
RIP: 0010:syscall_enter_from_user_mode+0x37/0x220 kernel/entry/common.c:112
Code: 49 89 fe 48 8b 7c 24 30 e8 f6 fa ff ff 0f 1f 44 00 00 0f 1f 44 00 00 e8 57 73 0c f7 e8 d2 71 0c f7 fb 65 4c 8b 3d c9 53 7e 75 <49> 8b 6f 08 40 f6 c5 3f 0f 84 b5 00 00 00 40 f6 c5 20 74 17 4c 89
RSP: 0018:ffffc9000aa3fef8 EFLAGS: 00000282
RAX: 3229529ed05bbe00 RBX: 00000000000000ca RCX: ffffffff91a84103
RDX: dffffc0000000000 RSI: ffffffff8aebd220 RDI: ffffffff8b3ccd60
RBP: ffffc9000aa3ff48 R08: dffffc0000000000 R09: fffffbfff1ca663e
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: ffffc9000aa3ff58 R15: ffff88808586bb80
do_syscall_64+0x1e/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc49748c389
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc49816d218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007fc4975ac058 RCX: 00007fc49748c389
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fc4975ac058
RBP: 00007fc4975ac050 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fc4975ac05c
R13: 00007fffdf0718df R14: 00007fc49816d300 R15: 0000000000022000
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, 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: 0f4ac6b4c5f0 Linux 6.1.37
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16a5d63ca80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b078ded3c2c9e539
dashboard link: https://syzkaller.appspot.com/bug?extid=00eb717e1ccc483c54e7
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/07d69feeab55/disk-0f4ac6b4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9668616ecc4b/vmlinux-0f4ac6b4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/bab83d45dde7/bzImage-0f4ac6b4.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+00eb71...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 1-...!: (0 ticks this GP) idle=924c/1/0x4000000000000000 softirq=108658/108658 fqs=0
(detected by 0, t=10502 jiffies, g=154257, q=82 ncpus=2)
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 2171 Comm: syz-executor.1 Not tainted 6.1.37-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:hlock_class kernel/locking/lockdep.c:228 [inline]
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4731 [inline]
RIP: 0010:__lock_acquire+0x552/0x1f80 kernel/locking/lockdep.c:5006
Code: 41 8b 1e 81 e3 ff 1f 00 00 48 89 d8 48 c1 e8 06 48 8d 3c c5 20 c2 28 90 be 08 00 00 00 e8 16 65 76 00 48 0f a3 1d 9e e4 be 0e <73> 1f 48 8d 04 5b 48 c1 e0 06 48 8d 98 20 21 f8 8f 48 ba 00 00 00
RSP: 0018:ffffc900001e0a00 EFLAGS: 00000057
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffffffff8169dd7a
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff9028c220
RBP: 0000000000000002 R08: dffffc0000000000 R09: fffffbfff2051845
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88808586c658
R13: ffff88808586bb80 R14: ffff88808586c6a8 R15: 1ffff11010b0d8d5
FS: 00007fc49816d700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30821000 CR3: 000000007866b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
debug_object_deactivate+0x61/0x3f0 lib/debugobjects.c:763
debug_hrtimer_deactivate kernel/time/hrtimer.c:425 [inline]
debug_deactivate+0x1d/0x280 kernel/time/hrtimer.c:481
__run_hrtimer kernel/time/hrtimer.c:1653 [inline]
__hrtimer_run_queues+0x334/0xe50 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:__syscall_enter_from_user_work kernel/entry/common.c:91 [inline]
RIP: 0010:syscall_enter_from_user_mode+0x37/0x220 kernel/entry/common.c:112
Code: 49 89 fe 48 8b 7c 24 30 e8 f6 fa ff ff 0f 1f 44 00 00 0f 1f 44 00 00 e8 57 73 0c f7 e8 d2 71 0c f7 fb 65 4c 8b 3d c9 53 7e 75 <49> 8b 6f 08 40 f6 c5 3f 0f 84 b5 00 00 00 40 f6 c5 20 74 17 4c 89
RSP: 0018:ffffc9000aa3fef8 EFLAGS: 00000282
RAX: 3229529ed05bbe00 RBX: 00000000000000ca RCX: ffffffff91a84103
RDX: dffffc0000000000 RSI: ffffffff8aebd220 RDI: ffffffff8b3ccd60
RBP: ffffc9000aa3ff48 R08: dffffc0000000000 R09: fffffbfff1ca663e
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: ffffc9000aa3ff58 R15: ffff88808586bb80
do_syscall_64+0x1e/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc49748c389
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc49816d218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007fc4975ac058 RCX: 00007fc49748c389
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fc4975ac058
RBP: 00007fc4975ac050 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fc4975ac05c
R13: 00007fffdf0718df R14: 00007fc49816d300 R15: 0000000000022000
</TASK>
rcu: rcu_preempt kthread timer wakeup didn't happen for 10501 jiffies! g154257 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: Possible timer handling issue on cpu=1 timer-softirq=129375
rcu: rcu_preempt kthread starved for 10502 jiffies! g154257 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:I stack:25432 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1935
rcu_gp_fqs_loop+0x2c2/0x1010 kernel/rcu/tree.c:1661
rcu_gp_kthread+0xa3/0x3a0 kernel/rcu/tree.c:1860
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 2171 Comm: syz-executor.1 Not tainted 6.1.37-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:101 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:128 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:159 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline]
RIP: 0010:kasan_check_range+0x5f/0x290 mm/kasan/generic.c:189
Code: eb 03 49 b8 00 00 00 00 00 fc ff df 4e 8d 0c 03 4c 8d 54 37 ff 49 c1 ea 03 49 bb 01 00 00 00 00 fc ff df 4f 8d 34 1a 4c 89 f5 <4c> 29 cd 48 83 fd 10 7f 26 48 85 ed 0f 84 3a 01 00 00 49 f7 d2 49
RSP: 0018:ffffc900001e09d8 EFLAGS: 00000803
RAX: 0000000000000001 RBX: 1ffffffff1ca663d RCX: ffffffff8169d23b
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8e5331e8
RBP: fffffbfff1ca663e R08: dffffc0000000000 R09: fffffbfff1ca663d
R10: 1ffffffff1ca663d R11: dffffc0000000001 R12: 1ffff9200003c148
R13: dffffc0000000000 R14: fffffbfff1ca663e R15: dffffc0000000000
FS: 00007fc49816d700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30821000 CR3: 000000007866b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
instrument_atomic_read include/linux/instrumented.h:72 [inline]
_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
cpumask_test_cpu include/linux/cpumask.h:444 [inline]
cpu_online include/linux/cpumask.h:1030 [inline]
trace_lock_acquire include/trace/events/lock.h:24 [inline]
lock_acquire+0xeb/0x5a0 kernel/locking/lockdep.c:5640
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
debug_object_activate+0x16b/0x860 lib/debugobjects.c:697
debug_hrtimer_activate kernel/time/hrtimer.c:420 [inline]
debug_activate kernel/time/hrtimer.c:475 [inline]
enqueue_hrtimer+0x30/0x390 kernel/time/hrtimer.c:1084
__run_hrtimer kernel/time/hrtimer.c:1702 [inline]
__hrtimer_run_queues+0x728/0xe50 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:__syscall_enter_from_user_work kernel/entry/common.c:91 [inline]
RIP: 0010:syscall_enter_from_user_mode+0x37/0x220 kernel/entry/common.c:112
Code: 49 89 fe 48 8b 7c 24 30 e8 f6 fa ff ff 0f 1f 44 00 00 0f 1f 44 00 00 e8 57 73 0c f7 e8 d2 71 0c f7 fb 65 4c 8b 3d c9 53 7e 75 <49> 8b 6f 08 40 f6 c5 3f 0f 84 b5 00 00 00 40 f6 c5 20 74 17 4c 89
RSP: 0018:ffffc9000aa3fef8 EFLAGS: 00000282
RAX: 3229529ed05bbe00 RBX: 00000000000000ca RCX: ffffffff91a84103
RDX: dffffc0000000000 RSI: ffffffff8aebd220 RDI: ffffffff8b3ccd60
RBP: ffffc9000aa3ff48 R08: dffffc0000000000 R09: fffffbfff1ca663e
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: ffffc9000aa3ff58 R15: ffff88808586bb80
do_syscall_64+0x1e/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc49748c389
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc49816d218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007fc4975ac058 RCX: 00007fc49748c389
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fc4975ac058
RBP: 00007fc4975ac050 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fc4975ac05c
R13: 00007fffdf0718df R14: 00007fc49816d300 R15: 0000000000022000
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Oct 13, 2023, 2:46:37 AM10/13/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages