Hello,
syzbot found the following issue on:
HEAD commit: 1a3746ccbb0a Merge tag 'strncpy-removal-v7.2-rc1' of git:/..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=113256ae580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=f5fece1a9477c321
dashboard link:
https://syzkaller.appspot.com/bug?extid=085adc3f91549d11066a
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=15b66ba1580000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=108f07f2580000
Downloadable assets:
disk image (non-bootable):
https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-1a3746cc.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/376997b632fc/vmlinux-1a3746cc.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/0920309c4838/bzImage-1a3746cc.xz
mounted in repro:
https://storage.googleapis.com/syzbot-assets/d394e1f93e2a/mount_2.gz
fsck result: OK (log:
https://syzkaller.appspot.com/x/fsck.log?x=10adbeae580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+085adc...@syzkaller.appspotmail.com
------------[ cut here ]------------
len > ordered->bytes_left
WARNING: fs/btrfs/ordered-data.c:390 at can_finish_ordered_extent+0x409/0x830 fs/btrfs/ordered-data.c:390, CPU#0: kworker/u4:9/1149
Modules linked in:
CPU: 0 UID: 0 PID: 1149 Comm: kworker/u4:9 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Workqueue: btrfs-endio simple_end_io_work
RIP: 0010:can_finish_ordered_extent+0x409/0x830 fs/btrfs/ordered-data.c:390
Code: 00 00 00 e8 09 81 c8 fd eb 05 e8 02 81 c8 fd 4d 85 ed 0f 94 c0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f 5d e9 09 92 b5 07 cc 90 <0f> 0b 90 e8 2f fd ad fd 48 8d 05 00 00 00 00 48 c7 c7 a0 9b 95 8e
RSP: 0018:ffffc900015bf968 EFLAGS: 00010287
RAX: ffffffff83fdc133 RBX: 1ffff11007f3479e RCX: ffff888032faa540
RDX: 0000000000000000 RSI: 0000000000006000 RDI: 0000000000071000
RBP: 1ffff11007f347a3 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff520002b7f2c R12: ffff88803f9a3cf0
R13: fffffffffff95000 R14: 1ffff110084b063c R15: 0000000000071000
FS: 0000000000000000(0000) GS:ffff88808c848000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb7eda7a000 CR3: 00000000439b1000 CR4: 0000000000352ef0
Call Trace:
<TASK>
btrfs_finish_ordered_extent+0xed/0x420 fs/btrfs/ordered-data.c:438
end_bbio_data_write+0xad3/0xc80 fs/btrfs/extent_io.c:538
btrfs_bio_end_io+0x3ea/0x4d0 fs/btrfs/bio.c:147
process_one_work kernel/workqueue.c:3322 [inline]
process_scheduled_works+0xa8e/0x14e0 kernel/workqueue.c:3405
worker_thread+0xa47/0xfb0 kernel/workqueue.c:3486
kthread+0x388/0x470 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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 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.
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