From: syzbot <syzbot+ba2afde329fc27e3f22e@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in btrfs_alloc_ordered_extent
Date: Wed, 24 Jun 2026 11:17:31 -0700 [thread overview]
Message-ID: <6a3c1f3b.4cbe3da0.2204f7.0162.GAE@google.com> (raw)
In-Reply-To: <6a39275b.5031c61f.34f2da.0001.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 840ef6c78e6a Merge tag 'nfs-for-7.2-1' of git://git.linux-..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=154b6591580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4b70f7c595323ba2
dashboard link: https://syzkaller.appspot.com/bug?extid=ba2afde329fc27e3f22e
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1005b21c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11e168dc580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/21afc0da735a/disk-840ef6c7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c89b2edbb4f6/vmlinux-840ef6c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/bef6a8464d41/bzImage-840ef6c7.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/33eb3874c00f/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=11009d0e580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ba2afde329fc27e3f22e@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/btrfs/ordered-data.c:264!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 1 UID: 0 PID: 6897 Comm: syz.4.79 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:insert_ordered_extent fs/btrfs/ordered-data.c:261 [inline]
RIP: 0010:btrfs_alloc_ordered_extent+0x943/0xad0 fs/btrfs/ordered-data.c:336
Code: 62 8d ba 08 01 00 00 b9 ef ff ff ff 49 c7 c0 20 15 97 8b 4d 89 f9 ff 75 00 41 54 41 55 41 56 53 e8 a2 54 37 fd 48 83 c4 28 90 <0f> 0b e8 c6 1d d2 fd 48 c7 c7 80 0c 97 8b 48 c7 c6 e0 0c 97 8b 48
RSP: 0018:ffffc90006e0e890 EFLAGS: 00010296
RAX: 45aae1616d386000 RBX: 0000000000069000 RCX: 1ffff92000dc1cf0
RDX: 0000000000000003 RSI: ffffffff8d89f46f RDI: ffff888028618000
RBP: ffff88806168cfe0 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff52000dc1c61 R12: 0000000000069000
R13: 0000000000004000 R14: 0000000000001089 R15: 0000000000004000
FS: 00007f50b1dee6c0(0000) GS:ffff88812621d000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007efc8ea98d50 CR3: 0000000045856000 CR4: 00000000003526f0
Call Trace:
<TASK>
cow_one_range fs/btrfs/inode.c:1241 [inline]
cow_file_range+0x744/0x12a0 fs/btrfs/inode.c:1403
fallback_to_cow+0x5ea/0xa00 fs/btrfs/inode.c:1751
run_delalloc_nocow+0x110c/0x17a0 fs/btrfs/inode.c:2181
btrfs_run_delalloc_range+0xbe4/0x1c20 fs/btrfs/inode.c:2419
writepage_delalloc+0x104d/0x1ba0 fs/btrfs/extent_io.c:1558
extent_writepage fs/btrfs/extent_io.c:1930 [inline]
extent_write_cache_pages fs/btrfs/extent_io.c:2593 [inline]
btrfs_writepages+0x1667/0x28b0 fs/btrfs/extent_io.c:2725
do_writepages+0x338/0x560 mm/page-writeback.c:2571
filemap_writeback mm/filemap.c:387 [inline]
filemap_fdatawrite_range+0x1f2/0x300 mm/filemap.c:412
btrfs_fdatawrite_range+0x54/0xf0 fs/btrfs/file.c:3884
btrfs_direct_write+0x6a0/0xc30 fs/btrfs/direct-io.c:1038
btrfs_do_write_iter+0x329/0x790 fs/btrfs/file.c:1449
do_iter_readv_writev+0x624/0x8d0 fs/read_write.c:-1
vfs_writev+0x34c/0x990 fs/read_write.c:1058
do_pwritev fs/read_write.c:1154 [inline]
__do_sys_pwritev2 fs/read_write.c:1212 [inline]
__se_sys_pwritev2+0x17a/0x2a0 fs/read_write.c:1203
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f50b278ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f50b1dee028 EFLAGS: 00000246 ORIG_RAX: 0000000000000148
RAX: ffffffffffffffda RBX: 00007f50b2a05fa0 RCX: 00007f50b278ce59
RDX: 0000000000000020 RSI: 0000200000000240 RDI: 0000000000000004
RBP: 00007f50b2822e6f R08: 0000000000000000 R09: 0000000000000003
R10: 0000000000003000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f50b2a06038 R14: 00007f50b2a05fa0 R15: 00007ffce174b008
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:insert_ordered_extent fs/btrfs/ordered-data.c:261 [inline]
RIP: 0010:btrfs_alloc_ordered_extent+0x943/0xad0 fs/btrfs/ordered-data.c:336
Code: 62 8d ba 08 01 00 00 b9 ef ff ff ff 49 c7 c0 20 15 97 8b 4d 89 f9 ff 75 00 41 54 41 55 41 56 53 e8 a2 54 37 fd 48 83 c4 28 90 <0f> 0b e8 c6 1d d2 fd 48 c7 c7 80 0c 97 8b 48 c7 c6 e0 0c 97 8b 48
RSP: 0018:ffffc90006e0e890 EFLAGS: 00010296
RAX: 45aae1616d386000 RBX: 0000000000069000 RCX: 1ffff92000dc1cf0
RDX: 0000000000000003 RSI: ffffffff8d89f46f RDI: ffff888028618000
RBP: ffff88806168cfe0 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff52000dc1c61 R12: 0000000000069000
R13: 0000000000004000 R14: 0000000000001089 R15: 0000000000004000
FS: 00007f50b1dee6c0(0000) GS:ffff88812621d000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007efc8ea98d50 CR3: 0000000045856000 CR4: 00000000003526f0
---
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.
prev parent reply other threads:[~2026-06-24 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 12:15 [syzbot] [btrfs?] kernel BUG in btrfs_alloc_ordered_extent syzbot
2026-06-24 18:17 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a3c1f3b.4cbe3da0.2204f7.0162.GAE@google.com \
--to=syzbot+ba2afde329fc27e3f22e@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox