[v6.1] INFO: rcu detected stall in sys_futex

11 views
Skip to first unread message

syzbot

unread,
Jul 5, 2023, 7:35:48 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=14f0fce8a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b078ded3c2c9e539
dashboard link: https://syzkaller.appspot.com/bug?extid=97f2ac670e5e7a3b48e4
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+97f2ac...@syzkaller.appspotmail.com

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...!: (0 ticks this GP) idle=fc04/1/0x4000000000000000 softirq=58477/58477 fqs=0
(detected by 1, t=10506 jiffies, g=79669, q=90 ncpus=2)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 19292 Comm: syz-executor.3 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:223 [inline]
RIP: 0010:mark_lock+0x61/0x340 kernel/locking/lockdep.c:4613
Code: 85 83 02 00 00 31 ed f6 43 02 03 40 0f 94 c5 83 f5 09 eb 0b 89 d5 83 fa 20 0f 83 d2 02 00 00 41 be 01 00 00 00 89 e9 41 d3 e6 <49> 8d 5f 20 48 89 d8 48 c1 e8 03 42 0f b6 04 28 84 c0 0f 85 29 02
RSP: 0018:ffffc90000007a18 EFLAGS: 00000006
RAX: 0000000000000000 RBX: ffff88806574a8c0 RCX: 0000000000000009
RDX: 0000000000000008 RSI: ffff88806574a8a0 RDI: ffff888065749dc0
RBP: 0000000000000009 R08: dffffc0000000000 R09: fffffbfff2051845
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88806574a898
R13: dffffc0000000000 R14: 0000000000000200 R15: ffff88806574a8a0
FS: 00005555558e5400(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000040 CR3: 00000000897b4000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
mark_usage kernel/locking/lockdep.c:4556 [inline]
__lock_acquire+0xc6a/0x1f80 kernel/locking/lockdep.c:5010
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:306
rcu_read_lock include/linux/rcupdate.h:747 [inline]
advance_sched+0x6ce/0x940 net/sched/sch_taprio.c:753
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x5e5/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:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0xd4/0x130 kernel/locking/spinlock.c:194
Code: 9c 8f 44 24 20 42 80 3c 23 00 74 08 4c 89 f7 e8 c2 61 52 f7 f6 44 24 21 02 75 4e 41 f7 c7 00 02 00 00 74 01 fb bf 01 00 00 00 <e8> 67 13 d0 f6 65 8b 05 e8 8f 74 75 85 c0 74 3f 48 c7 04 24 0e 36
RSP: 0018:ffffc9000320fa20 EFLAGS: 00000206
RAX: 55d530471a1dc200 RBX: 1ffff92000641f48 RCX: ffffffff91a84103
RDX: dffffc0000000000 RSI: ffffffff8aebd220 RDI: 0000000000000001
RBP: ffffc9000320fab0 R08: dffffc0000000000 R09: ffffed100ec814f9
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff92000641f44 R14: ffffc9000320fa40 R15: 0000000000000246
try_to_wake_up+0x7dd/0x12b0 kernel/sched/core.c:4226
wake_up_process kernel/sched/core.c:4358 [inline]
wake_up_q+0x8b/0xd0 kernel/sched/core.c:1007
futex_wake+0x4ea/0x590 kernel/futex/waitwake.c:184
do_futex+0x375/0x490 kernel/futex/syscalls.c:111
__do_sys_futex kernel/futex/syscalls.c:183 [inline]
__se_sys_futex+0x3d7/0x460 kernel/futex/syscalls.c:164
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:0x7fb6d228c389
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:00007ffe46578868 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007fb6d23abf8c RCX: 00007fb6d228c389
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 00007fb6d23abf88
RBP: 00007fb6d23abf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fb6d23abf8c
R13: 00007fb6d1e002d8 R14: 00007fb6d23abf80 R15: 0000000000000000
</TASK>
rcu: rcu_preempt kthread timer wakeup didn't happen for 10505 jiffies! g79669 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: Possible timer handling issue on cpu=0 timer-softirq=78596
rcu: rcu_preempt kthread starved for 10506 jiffies! g79669 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0
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:24888 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 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 19292 Comm: syz-executor.3 Not tainted 6.1.37-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:validate_chain+0x5f0/0x58e0 kernel/locking/lockdep.c:3844
Code: 01 00 00 0e 36 e0 45 49 c7 04 04 00 00 00 00 49 c7 44 04 09 00 00 00 00 49 c7 44 04 17 00 00 00 00 49 c7 44 04 23 00 00 00 00 <41> c6 44 04 2b 00 65 48 8b 04 25 28 00 00 00 48 3b 84 24 60 02 00
RSP: 0018:ffffc900000077c0 EFLAGS: 00000002
RAX: 1ffff92000000f18 RBX: ffffffff9028dda0 RCX: ffffffff816a8b15
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff9028c228
RBP: ffffc90000007a70 R08: dffffc0000000000 R09: fffffbfff2051846
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88806574a8c0 R14: 0000000000000001 R15: ffffffff9028ddb8
FS: 00005555558e5400(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000040 CR3: 00000000897b4000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
__lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
__raw_spin_lock_irq include/linux/spinlock_api_smp.h:119 [inline]
_raw_spin_lock_irq+0xcf/0x110 kernel/locking/spinlock.c:170
__run_hrtimer kernel/time/hrtimer.c:1689 [inline]
__hrtimer_run_queues+0x6d3/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:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0xd4/0x130 kernel/locking/spinlock.c:194
Code: 9c 8f 44 24 20 42 80 3c 23 00 74 08 4c 89 f7 e8 c2 61 52 f7 f6 44 24 21 02 75 4e 41 f7 c7 00 02 00 00 74 01 fb bf 01 00 00 00 <e8> 67 13 d0 f6 65 8b 05 e8 8f 74 75 85 c0 74 3f 48 c7 04 24 0e 36
RSP: 0018:ffffc9000320fa20 EFLAGS: 00000206
RAX: 55d530471a1dc200 RBX: 1ffff92000641f48 RCX: ffffffff91a84103
RDX: dffffc0000000000 RSI: ffffffff8aebd220 RDI: 0000000000000001
RBP: ffffc9000320fab0 R08: dffffc0000000000 R09: ffffed100ec814f9
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff92000641f44 R14: ffffc9000320fa40 R15: 0000000000000246
try_to_wake_up+0x7dd/0x12b0 kernel/sched/core.c:4226
wake_up_process kernel/sched/core.c:4358 [inline]
wake_up_q+0x8b/0xd0 kernel/sched/core.c:1007
futex_wake+0x4ea/0x590 kernel/futex/waitwake.c:184
do_futex+0x375/0x490 kernel/futex/syscalls.c:111
__do_sys_futex kernel/futex/syscalls.c:183 [inline]
__se_sys_futex+0x3d7/0x460 kernel/futex/syscalls.c:164
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:0x7fb6d228c389
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:00007ffe46578868 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007fb6d23abf8c RCX: 00007fb6d228c389
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 00007fb6d23abf88
RBP: 00007fb6d23abf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fb6d23abf8c
R13: 00007fb6d1e002d8 R14: 00007fb6d23abf80 R15: 0000000000000000
</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

unread,
Jul 11, 2023, 1:38:56 AM7/11/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17e7ddf8a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=61785ceccc6bdf75
dashboard link: https://syzkaller.appspot.com/bug?extid=a4b1213abbe3ecd9ed41
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df6c88d1a764/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/787a9f4e718c/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4a60832537ff/Image-d54cfc42.gz.xz

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

ip6_tunnel: ip6tnl1 xmit: Local address not yet configured!
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...0: (1 GPs behind) idle=00b/1/0x4000000000000002 softirq=13040/13047 fqs=5247
(detected by 1, t=10502 jiffies, g=15109, q=2742)
Task dump for CPU 0:
task:syz-executor.4 state:R running task stack: 0 pid: 6674 ppid: 4003 flags:0x00000003
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
__enter_from_kernel_mode arch/arm64/kernel/entry-common.c:51 [inline]
enter_from_kernel_mode+0x98/0x17c arch/arm64/kernel/entry-common.c:56
el1_interrupt+0x30/0x58 arch/arm64/kernel/entry-common.c:442
el1h_64_irq_handler+0x18/0x24 arch/arm64/kernel/entry-common.c:458
el1h_64_irq+0x78/0x7c arch/arm64/kernel/entry.S:580
arch_local_irq_restore arch/arm64/include/asm/irqflags.h:122 [inline]
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
_raw_spin_unlock_irqrestore+0xbc/0x158 kernel/locking/spinlock.c:194
try_to_wake_up+0x488/0xc2c kernel/sched/core.c:4144
wake_up_process kernel/sched/core.c:4211 [inline]
wake_up_q+0xa4/0x124 kernel/sched/core.c:950
futex_wake+0x538/0x644 kernel/futex/core.c:1692
do_futex+0xf90/0x2d88 kernel/futex/core.c:3977
__do_sys_futex kernel/futex/core.c:4049 [inline]
__se_sys_futex kernel/futex/core.c:4030 [inline]
__arm64_sys_futex+0x424/0x498 kernel/futex/core.c:4030
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

syzbot

unread,
Apr 10, 2024, 1:08:15 PMApr 10
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