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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2a910f4af54d Linux 5.15.139
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=119c82cce80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4901940b923cf2ea
dashboard link: https://syzkaller.appspot.com/bug?extid=ff0df46d5a3087ce54ea
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/3635f683392f/disk-2a910f4a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e6fa88fc3919/vmlinux-2a910f4a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c376027e57f4/bzImage-2a910f4a.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 1-...0: (0 ticks this GP) idle=a4d/1/0x4000000000000000 softirq=215785/215785 fqs=2099
(detected by 0, t=10502 jiffies, g=273585, q=240)
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 28093 Comm: syz-executor.1 Not tainted 5.15.139-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:kasan_mem_to_shadow include/linux/kasan.h:55 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:129 [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+0x4a/0x290 mm/kasan/generic.c:189
Code: 48 c1 ed 2f 81 fd ff ff 01 00 0f 82 46 02 00 00 48 89 fb 48 c1 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
RSP: 0018:ffffc90000dd0a38 EFLAGS: 00000802
RAX: 0000000000000001 RBX: 1ffffffff1f79c20 RCX: ffffffff816290df
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8fbce100
RBP: 000000000001ffff R08: dffffc0000000000 R09: fffffbfff1f79c20
R10: ffffffff8fbce107 R11: dffffc0000000001 R12: 0000000000000004
R13: ffff88801c36c668 R14: 1ffff1100386d8e6 R15: ffff88801c36c730
FS: 00007f848e7f66c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020390000 CR3: 00000000998b2000 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:71 [inline]
test_bit include/asm-generic/bitops/instrumented-non-atomic.h:134 [inline]
__lock_acquire+0xcef/0x1ff0 kernel/locking/lockdep.c:4981
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:269
rcu_read_lock include/linux/rcupdate.h:696 [inline]
advance_sched+0x6ce/0x940 net/sched/sch_taprio.c:769
__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: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+0x5c/0x290 mm/kasan/generic.c:189
Code: fb 48 c1 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
RSP: 0018:ffffc9000c23f798 EFLAGS: 00000a03
RAX: ffffffff81e53801 RBX: 1ffffd4000408a20 RCX: ffffffff81e53831
RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffea0002045100
RBP: 000000000001ffff R08: dffffc0000000000 R09: fffff94000408a20
R10: 1ffffd4000408a20 R11: dffffc0000000001 R12: 00fff00000002011
R13: dffffc0000000000 R14: fffff94000408a21 R15: ffffea0002045108
instrument_atomic_read_write include/linux/instrumented.h:101 [inline]
test_and_set_bit include/asm-generic/bitops/instrumented-atomic.h:70 [inline]
TestSetPageDirty include/linux/page-flags.h:348 [inline]
mark_buffer_dirty+0x271/0x4b0 fs/buffer.c:1105
__block_commit_write+0x1db/0x310 fs/buffer.c:2085
block_write_end fs/buffer.c:2164 [inline]
generic_write_end+0xa7/0x440 fs/buffer.c:2178
ext4_da_write_end+0x72d/0x9e0 fs/ext4/inode.c:3084
generic_perform_write+0x3b7/0x5b0 mm/filemap.c:3787
ext4_buffered_write_iter+0x227/0x360 fs/ext4/file.c:268
ext4_file_write_iter+0x87c/0x1990
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:0x7f8490274ae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f848e7f60c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f8490393f80 RCX: 00007f8490274ae9
RDX: 000000000208e24b RSI: 0000000020000000 RDI: 0000000000000003
RBP: 00007f84902c047a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f8490393f80 R15: 00007fff7db4a838
</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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.