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

0 views
Skip to first unread message

syzbot

unread,
Mar 8, 2024, 1:29:30 PMMar 8
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 574362648507 Linux 5.15.151
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15d54ba6180000
kernel config: https://syzkaller.appspot.com/x/.config?x=6c9a42d9e3519ca9
dashboard link: https://syzkaller.appspot.com/bug?extid=bb21d42787b313521a4c
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/f00d4062000b/disk-57436264.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3a74c2b6ca62/vmlinux-57436264.xz
kernel image: https://storage.googleapis.com/syzbot-assets/93bd706dc219/bzImage-57436264.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...!: (0 ticks this GP) idle=b83/1/0x4000000000000000 softirq=50431/50431 fqs=0
(detected by 1, t=10502 jiffies, g=75053, q=81)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 2944 Comm: syslogd Not tainted 5.15.151-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:lock_release+0xd/0x9a0 kernel/locking/lockdep.c:5631
Code: c1 03 38 c1 0f 8c 6b fd ff ff 48 89 df e8 8b 44 67 00 e9 5e fd ff ff 66 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 53 <48> 83 e4 e0 48 81 ec 00 01 00 00 49 89 f5 48 89 7c 24 20 65 48 8b
RSP: 0018:ffffc90000007c88 EFLAGS: 00000086
RAX: f3f3f300f1f1f1f1 RBX: ffff8880b9a2a200 RCX: 0000000000000001
RDX: 0000000080010001 RSI: ffffffff816f3dec RDI: ffff8880b9a2a218
RBP: ffffc90000007cb0 R08: ffffffff816f3d80 R09: fffffbfff1bc719e
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff92000000f98 R14: ffffc90000007ce0 R15: 0000000000000046
FS: 00007f9ab126d380(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb8f8029000 CR3: 0000000022eba000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:158 [inline]
_raw_spin_unlock_irqrestore+0x75/0x130 kernel/locking/spinlock.c:194
__run_hrtimer kernel/time/hrtimer.c:1682 [inline]
__hrtimer_run_queues+0x48c/0xcf0 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
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:seqcount_lockdep_reader_access+0x1dc/0x220 include/linux/seqlock.h:106
Code: 00 4d 85 ed 75 16 e8 f3 b0 10 00 eb 15 e8 ec b0 10 00 e8 57 24 ac 08 4d 85 ed 74 ea e8 dd b0 10 00 fb 48 c7 04 24 0e 36 e0 45 <4b> c7 04 3c 00 00 00 00 66 43 c7 44 3c 09 00 00 43 c6 44 3c 0b 00
RSP: 0018:ffffc9000b607980 EFLAGS: 00000293
RAX: ffffffff816f84b3 RBX: 0000000000000000 RCX: ffff8880246dbb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000b607a28 R08: ffffffff816f8489 R09: fffffbfff1f79e2a
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000200 R14: 0000000000000046 R15: 1ffff920016c0f30
ktime_get_coarse_real_ts64+0x36/0x120 kernel/time/timekeeping.c:2244
current_time+0x87/0x2f0 fs/inode.c:2327
file_update_time+0xd9/0x460 fs/inode.c:2002
__generic_file_write_iter+0x1ad/0x4f0 mm/filemap.c:3862
generic_file_write_iter+0xa7/0x1b0 mm/filemap.c:3944
call_write_iter include/linux/fs.h:2148 [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:0x7f9ab13c1bf2
Code: 89 c7 48 89 44 24 08 e8 7b 34 fa ff 48 8b 44 24 08 48 83 c4 28 c3 c3 64 8b 04 25 18 00 00 00 85 c0 75 20 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 76 6f 48 8b 15 07 a2 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffe353ce948 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f9ab13c1bf2
RDX: 0000000000000113 RSI: 0000561d2f769c50 RDI: 0000000000000003
RBP: 0000561d2f769c50 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000001000 R11: 0000000000000246 R12: 0000000000000113
R13: 00007f9ab126d300 R14: 0000000000000005 R15: 0000561d2f769a60
</TASK>
rcu: rcu_preempt kthread timer wakeup didn't happen for 10501 jiffies! g75053 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: Possible timer handling issue on cpu=0 timer-softirq=36784
rcu: rcu_preempt kthread starved for 10502 jiffies! g75053 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:27000 pid: 15 ppid: 2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1884
rcu_gp_fqs_loop+0x2bf/0x1080 kernel/rcu/tree.c:1972
rcu_gp_kthread+0xa4/0x360 kernel/rcu/tree.c:2145
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: 2944 Comm: syslogd Not tainted 5.15.151-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:kasan_check_range+0x5/0x290 mm/kasan/generic.c:188
Code: c7 e8 0f 57 52 08 31 c0 c3 0f 0b b8 ea ff ff ff c3 0f 0b b8 ea ff ff ff c3 cc cc cc cc cc cc cc cc cc cc cc cc 55 41 57 41 56 <53> b0 01 48 85 f6 0f 84 9a 01 00 00 48 89 fd 48 01 f5 0f 82 59 02
RSP: 0018:ffffc900000079f8 EFLAGS: 00000046
RAX: 0000000000000033 RBX: 0000000000000ce1 RCX: ffffffff8162f4e8
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8fbcf258
RBP: 0000000000000008 R08: dffffc0000000000 R09: fffffbfff1f79e4c
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000002
R13: dffffc0000000000 R14: 0000000000000100 R15: ffff8880246dc6c0
FS: 00007f9ab126d380(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb8f8029000 CR3: 0000000022eba000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
instrument_atomic_read include/linux/instrumented.h:71 [inline]
test_bit include/asm-generic/bitops/instrumented-non-atomic.h:134 [inline]
hlock_class kernel/locking/lockdep.c:197 [inline]
mark_lock+0x98/0x340 kernel/locking/lockdep.c:4569
mark_usage kernel/locking/lockdep.c:4512 [inline]
__lock_acquire+0xc97/0x1ff0 kernel/locking/lockdep.c:4966
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
__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:1686 [inline]
__hrtimer_run_queues+0x598/0xcf0 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
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:seqcount_lockdep_reader_access+0x1dc/0x220 include/linux/seqlock.h:106
Code: 00 4d 85 ed 75 16 e8 f3 b0 10 00 eb 15 e8 ec b0 10 00 e8 57 24 ac 08 4d 85 ed 74 ea e8 dd b0 10 00 fb 48 c7 04 24 0e 36 e0 45 <4b> c7 04 3c 00 00 00 00 66 43 c7 44 3c 09 00 00 43 c6 44 3c 0b 00
RSP: 0018:ffffc9000b607980 EFLAGS: 00000293
RAX: ffffffff816f84b3 RBX: 0000000000000000 RCX: ffff8880246dbb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000b607a28 R08: ffffffff816f8489 R09: fffffbfff1f79e2a
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000200 R14: 0000000000000046 R15: 1ffff920016c0f30
ktime_get_coarse_real_ts64+0x36/0x120 kernel/time/timekeeping.c:2244
current_time+0x87/0x2f0 fs/inode.c:2327
file_update_time+0xd9/0x460 fs/inode.c:2002
__generic_file_write_iter+0x1ad/0x4f0 mm/filemap.c:3862
generic_file_write_iter+0xa7/0x1b0 mm/filemap.c:3944
call_write_iter include/linux/fs.h:2148 [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:0x7f9ab13c1bf2
Code: 89 c7 48 89 44 24 08 e8 7b 34 fa ff 48 8b 44 24 08 48 83 c4 28 c3 c3 64 8b 04 25 18 00 00 00 85 c0 75 20 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 76 6f 48 8b 15 07 a2 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffe353ce948 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f9ab13c1bf2
RDX: 0000000000000113 RSI: 0000561d2f769c50 RDI: 0000000000000003
RBP: 0000561d2f769c50 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000001000 R11: 0000000000000246 R12: 0000000000000113
R13: 00007f9ab126d300 R14: 0000000000000005 R15: 0000561d2f769a60
</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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages