[v6.1] WARNING in fiemap_process_hole

0 views
Skip to first unread message

syzbot

unread,
Mar 5, 2025, 9:53:25 PM3/5/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3a8358583626 Linux 6.1.129
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1232c078580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d841937c118666c6
dashboard link: https://syzkaller.appspot.com/bug?extid=e9252738714e6a84d387
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/13f8e53cc467/disk-3a835858.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a85676a44932/vmlinux-3a835858.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e9dcc0eaae9/bzImage-3a835858.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 9872 at fs/btrfs/extent_io.c:3539 fiemap_process_hole+0xebb/0x1290 fs/btrfs/extent_io.c:3821
Modules linked in:
CPU: 1 PID: 9872 Comm: syz.6.1085 Not tainted 6.1.129-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:emit_fiemap_extent fs/btrfs/extent_io.c:3539 [inline]
RIP: 0010:fiemap_process_hole+0xebb/0x1290 fs/btrfs/extent_io.c:3821
Code: 89 44 24 10 4c 89 74 24 18 4a 8d 1c 30 48 89 df 4c 8b b4 24 90 00 00 00 4c 89 f6 e8 2f 95 ee fd 4c 39 f3 76 16 e8 45 93 ee fd <0f> 0b e9 19 01 00 00 e8 39 93 ee fd e9 ed 01 00 00 48 89 df 4c 89
RSP: 0018:ffffc900035c7520 EFLAGS: 00010287
RAX: ffffffff839c038b RBX: 0000000000101000 RCX: 0000000000080000
RDX: ffffc9000efa5000 RSI: 00000000000233d7 RDI: 00000000000233d8
RBP: ffffc900035c7688 R08: ffffffff839c0381 R09: fffffbfff2256c7c
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff920006b8f1f
R13: 00000000000ff000 R14: 0000000000002000 R15: 1ffff920006b8f1e
FS: 00007f2e984336c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00004000000002a0 CR3: 000000007d79a000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
extent_fiemap+0xeb2/0x2310 fs/btrfs/extent_io.c:4030
btrfs_fiemap+0x174/0x1e0 fs/btrfs/inode.c:8290
ioctl_fiemap fs/ioctl.c:219 [inline]
do_vfs_ioctl+0x18e9/0x2a90 fs/ioctl.c:810
__do_sys_ioctl fs/ioctl.c:868 [inline]
__se_sys_ioctl+0x81/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f2e9758d169
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2e98433038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f2e977a5fa0 RCX: 00007f2e9758d169
RDX: 0000400000000280 RSI: 00000000c020660b RDI: 0000000000000004
RBP: 00007f2e9760e2a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f2e977a5fa0 R15: 00007ffccb47b568
</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

unread,
Jun 22, 2025, 3:23:14 PM6/22/25
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages