[v5.15] WARNING in __kernel_write

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 115472395b0a Linux 5.15.104
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1339a8a9c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5592cc4916e1c2f
dashboard link: https://syzkaller.appspot.com/bug?extid=f704b898b11e4a0a9a1f
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/6c2c0744c7e0/disk-11547239.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7ea4c5ecca4f/vmlinux-11547239.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9a231dbcf423/bzImage-11547239.xz

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

BTRFS info (device loop1): enabling ssd optimizations
------------[ cut here ]------------
WARNING: CPU: 1 PID: 2668 at fs/read_write.c:525 __kernel_write+0x8cc/0xa60
Modules linked in:
CPU: 1 PID: 2668 Comm: syz-executor.1 Not tainted 5.15.104-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:__kernel_write+0x8cc/0xa60 fs/read_write.c:525
Code: 25 28 00 00 00 48 3b 84 24 40 01 00 00 0f 85 a4 01 00 00 4c 89 f0 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 c4 e0 ab ff <0f> 0b 49 c7 c6 f7 ff ff ff eb 9d e8 b4 e0 ab ff eb 05 e8 ad e0 ab
RSP: 0018:ffffc9000112f7a0 EFLAGS: 00010283
RAX: ffffffff81d3d71c RBX: 00000000000a801d RCX: 0000000000040000
RDX: ffffc900101a6000 RSI: 0000000000001f97 RDI: 0000000000001f98
RBP: ffffc9000112f930 R08: ffffffff81d3cf90 R09: ffffc9000112f890
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92000225f00
R13: dffffc0000000000 R14: ffff888023d20584 R15: 0000000000000011
FS: 00007fddcb09c700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc9dbdde300 CR3: 000000006cc87000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
kernel_write+0xcd/0x200 fs/read_write.c:568
write_buf fs/btrfs/send.c:565 [inline]
send_header fs/btrfs/send.c:684 [inline]
send_subvol+0x188/0x4200 fs/btrfs/send.c:7385
btrfs_ioctl_send+0x193a/0x1d60 fs/btrfs/send.c:7711
_btrfs_ioctl_send+0x2fb/0x430 fs/btrfs/ioctl.c:4880
btrfs_ioctl+0x595/0xb10
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
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:0x7fddccb2a0f9
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:00007fddcb09c168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fddccc49f80 RCX: 00007fddccb2a0f9
RDX: 0000000020000140 RSI: 0000000040489426 RDI: 0000000000000003
RBP: 00007fddccb85b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe8b729e9f R14: 00007fddcb09c300 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.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 8a7f2a5c5aa1 Linux 5.15.110
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10cfe5f4280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e93d602da27af41

dashboard link: https://syzkaller.appspot.com/bug?extid=f704b898b11e4a0a9a1f
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16cb3522280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11cd72b8280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/16bea75b636d/disk-8a7f2a5c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b169e33dcf2/vmlinux-8a7f2a5c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/190d08a00950/Image-8a7f2a5c.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/01381288ce5d/mount_0.gz

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

BTRFS info (device loop0): using free space tree
BTRFS info (device loop0): has skinny extents
BTRFS info (device loop0): enabling ssd optimizations
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3968 at fs/read_write.c:525 __kernel_write+0x734/0x8b0
Modules linked in:
CPU: 1 PID: 3968 Comm: syz-executor352 Not tainted 5.15.110-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __kernel_write+0x734/0x8b0
lr : __kernel_write+0x730/0x8b0 fs/read_write.c:525
sp : ffff800018dc74e0
x29: ffff800018dc7650 x28: ffff7000031b8ea8 x27: ffff0000c92168e8
x26: 0000000000000011 x25: dfff800000000000 x24: 1fffe0001a272860
x23: ffff800018dc7560 x22: fffffffffffffff7 x21: ffff0000d1394304
x20: ffff800018dc7540 x19: ffff0000d1394280 x18: ffff800018dc7520
x17: 1fffe00036903d8e x16: ffff800011941c2c x15: 000000000000c369
x14: 1ffff0000291a06a x13: ffffffffffffffff x12: 0000000000000000
x11: ff8080000896c37c x10: 0000000000000000 x9 : ffff80000896c37c
x8 : ffff0000c8c8b580 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000020
x2 : 0000000000000008 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
__kernel_write+0x734/0x8b0
kernel_write+0xe0/0x1ec fs/read_write.c:568

write_buf fs/btrfs/send.c:565 [inline]
send_header fs/btrfs/send.c:684 [inline]

send_subvol+0x164/0x37cc fs/btrfs/send.c:7385
btrfs_ioctl_send+0x15b0/0x1a50 fs/btrfs/send.c:7711
_btrfs_ioctl_send+0x340/0x498 fs/btrfs/ioctl.c:4882
btrfs_ioctl+0x5e0/0xa5c

vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]

__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
__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
irq event stamp: 86118
hardirqs last enabled at (86117): [<ffff800008268c94>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1338 [inline]
hardirqs last enabled at (86117): [<ffff800008268c94>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:4780
hardirqs last disabled at (86118): [<ffff80001193d130>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (86052): [<ffff800008030068>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (86050): [<ffff800008030034>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace d3bd68682de7c9d7 ]---


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.