[v5.15] INFO: rcu detected stall in generic_file_write_iter

0 views
Skip to first unread message

syzbot

unread,
Sep 4, 2023, 1:16:10 PM9/4/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 8f790700c974 Linux 5.15.130
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=162a3913a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=a22cff001b9b10b3
dashboard link: https://syzkaller.appspot.com/bug?extid=0d5f70c68e62eb57d5c6
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/97d68b3e1757/disk-8f790700.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4ecbd3f0457b/vmlinux-8f790700.xz
kernel image: https://storage.googleapis.com/syzbot-assets/68019fbed619/bzImage-8f790700.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...!: (0 ticks this GP) idle=27b/1/0x4000000000000000 softirq=22586/22586 fqs=0
(detected by 1, t=10505 jiffies, g=35205, q=291)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 8313 Comm: syz-executor.5 Not tainted 5.15.130-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
RIP: 0010:arch_atomic_try_cmpxchg arch/x86/include/asm/atomic.h:202 [inline]
RIP: 0010:atomic_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:513 [inline]
RIP: 0010:queued_spin_lock include/asm-generic/qspinlock.h:82 [inline]
RIP: 0010:do_raw_spin_lock+0x150/0x370 kernel/locking/spinlock_debug.c:115
Code: 00 00 c7 44 24 60 00 00 00 00 4c 89 e7 be 04 00 00 00 e8 f3 cd 65 00 4c 89 f7 be 04 00 00 00 e8 e6 cd 65 00 41 0f b6 44 1d 00 <84> c0 48 89 da 0f 85 89 01 00 00 8b 44 24 60 b9 01 00 00 00 f0 41
RSP: 0018:ffffc90000007be0 EFLAGS: 00000097
RAX: 0000000000000004 RBX: dffffc0000000000 RCX: ffffffff8163f18a
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffc90000007c40
RBP: ffffc90000007cb0 R08: dffffc0000000000 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: ffff88801bddb2e8
R13: 1ffff92000000f88 R14: ffffc90000007c40 R15: 1ffff110037bb65e
FS: 00007feefd4b56c0(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1c02f4f988 CR3: 000000004225c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
spin_lock include/linux/spinlock.h:363 [inline]
advance_sched+0x47/0x940 net/sched/sch_taprio.c:716
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x598/0xcf0 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1085 [inline]
__sysvec_apic_timer_interrupt+0x139/0x470 arch/x86/kernel/apic/apic.c:1102
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1096
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:lru_cache_add+0x263/0x7e0 mm/swap.c:447
Code: e8 03 80 3c 28 00 74 08 48 89 df e8 67 ce 1d 00 4c 8b 23 48 c7 c7 ff ff ff ff 4c 89 e6 e8 75 31 d4 ff 48 8b 04 24 80 3c 28 00 <74> 08 4c 89 ff e8 43 ce 1d 00 4d 8b 2f 44 89 eb 83 e3 01 31 ff 48
RSP: 0018:ffffc90004d4f840 EFLAGS: 00000246
RAX: 1ffffd40002fe689 RBX: ffffea00017f3440 RCX: ffff888020f23b80
RDX: ffffc90002df1000 RSI: 00fff00000080003 RDI: ffffffffffffffff
RBP: dffffc0000000000 R08: ffffffff81abef7b R09: fffff940002fe689
R10: 0000000000000000 R11: dffffc0000000001 R12: 00fff00000080003
R13: ffffea00017f3440 R14: ffffea00017f3440 R15: ffffea00017f3448
shmem_getpage_gfp+0x1b6f/0x3190 mm/shmem.c:1945
shmem_getpage mm/shmem.c:151 [inline]
shmem_write_begin+0xce/0x1a0 mm/shmem.c:2477
generic_perform_write+0x2bf/0x5b0 mm/filemap.c:3776
__generic_file_write_iter+0x243/0x4f0 mm/filemap.c:3903
generic_file_write_iter+0xa7/0x1b0 mm/filemap.c:3935
call_write_iter include/linux/fs.h:2103 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xacf/0xe50 fs/read_write.c:594
ksys_write+0x1a2/0x2c0 fs/read_write.c:647
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+0x61/0xcb
RIP: 0033:0x7feefef3282f
Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 b9 80 02 00 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 0c 81 02 00 48
RSP: 002b:00007feefd4b4e70 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000001000000 RCX: 00007feefef3282f
RDX: 0000000001000000 RSI: 00007feef5095000 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000000 R09: 00000000000051a5
R10: 0000000020005282 R11: 0000000000000293 R12: 0000000000000003
R13: 00007feefd4b4f3c R14: 00007feefd4b4f40 R15: 00007feef5095000
</TASK>
rcu: rcu_preempt kthread timer wakeup didn't happen for 10504 jiffies! g35205 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: Possible timer handling issue on cpu=0 timer-softirq=26270
rcu: rcu_preempt kthread starved for 10505 jiffies! g35205 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:26200 pid: 15 ppid: 2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1884
rcu_gp_fqs_loop+0x2af/0xf70 kernel/rcu/tree.c:1959
rcu_gp_kthread+0xa4/0x360 kernel/rcu/tree.c:2132
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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: 8313 Comm: syz-executor.5 Not tainted 5.15.130-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
RIP: 0010:hlock_class kernel/locking/lockdep.c:197 [inline]
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4686 [inline]
RIP: 0010:__lock_acquire+0x551/0x1ff0 kernel/locking/lockdep.c:4961
Code: 00 00 41 8b 1f 81 e3 ff 1f 00 00 89 d8 c1 e8 06 48 8d 3c c5 00 81 bd 8f be 08 00 00 00 e8 c7 37 67 00 48 0f a3 1d 5f f9 5a 0e <73> 1f 48 8d 04 5b 48 c1 e0 06 48 8d 98 00 e0 8c 8f 48 ba 00 00 00
RSP: 0018:ffffc90000007a60 EFLAGS: 00000057
RAX: 0000000000000001 RBX: 0000000000000a0a RCX: ffffffff81628799
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8fbd8240
RBP: 000000000000000a R08: dffffc0000000000 R09: fffffbfff1f7b049
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000002
R13: ffff888020f24668 R14: 0000000000000002 R15: ffff888020f246e0
FS: 00007feefd4b56c0(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1c02f4f988 CR3: 000000004225c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:363 [inline]
advance_sched+0x47/0x940 net/sched/sch_taprio.c:716
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x598/0xcf0 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1085 [inline]
__sysvec_apic_timer_interrupt+0x139/0x470 arch/x86/kernel/apic/apic.c:1102
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1096
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:lru_cache_add+0x263/0x7e0 mm/swap.c:447
Code: e8 03 80 3c 28 00 74 08 48 89 df e8 67 ce 1d 00 4c 8b 23 48 c7 c7 ff ff ff ff 4c 89 e6 e8 75 31 d4 ff 48 8b 04 24 80 3c 28 00 <74> 08 4c 89 ff e8 43 ce 1d 00 4d 8b 2f 44 89 eb 83 e3 01 31 ff 48
RSP: 0018:ffffc90004d4f840 EFLAGS: 00000246
RAX: 1ffffd40002fe689 RBX: ffffea00017f3440 RCX: ffff888020f23b80
RDX: ffffc90002df1000 RSI: 00fff00000080003 RDI: ffffffffffffffff
RBP: dffffc0000000000 R08: ffffffff81abef7b R09: fffff940002fe689
R10: 0000000000000000 R11: dffffc0000000001 R12: 00fff00000080003
R13: ffffea00017f3440 R14: ffffea00017f3440 R15: ffffea00017f3448
shmem_getpage_gfp+0x1b6f/0x3190 mm/shmem.c:1945
shmem_getpage mm/shmem.c:151 [inline]
shmem_write_begin+0xce/0x1a0 mm/shmem.c:2477
generic_perform_write+0x2bf/0x5b0 mm/filemap.c:3776
__generic_file_write_iter+0x243/0x4f0 mm/filemap.c:3903
generic_file_write_iter+0xa7/0x1b0 mm/filemap.c:3935
call_write_iter include/linux/fs.h:2103 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xacf/0xe50 fs/read_write.c:594
ksys_write+0x1a2/0x2c0 fs/read_write.c:647
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+0x61/0xcb
RIP: 0033:0x7feefef3282f
Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 b9 80 02 00 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 0c 81 02 00 48
RSP: 002b:00007feefd4b4e70 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000001000000 RCX: 00007feefef3282f
RDX: 0000000001000000 RSI: 00007feef5095000 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000000 R09: 00000000000051a5
R10: 0000000020005282 R11: 0000000000000293 R12: 0000000000000003
R13: 00007feefd4b4f3c R14: 00007feefd4b4f40 R15: 00007feef5095000
</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 overwrite 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,
Dec 13, 2023, 12:16:16 PM12/13/23
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