[v5.15] WARNING in xfs_bmapi_convert_delalloc (2)

4 views
Skip to first unread message

syzbot

unread,
Apr 4, 2025, 3:22:23 AM4/4/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 0c935c049b5c Linux 5.15.179
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17eec94c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bcb6af887426ce59
dashboard link: https://syzkaller.appspot.com/bug?extid=9d988404f10c4ebd4189
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=139f27cf980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11110fb0580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/75b060834e1e/disk-0c935c04.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d42b06ae465d/vmlinux-0c935c04.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d5217676cd35/bzImage-0c935c04.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9a34a31dc462/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=157fd998580000)

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 1221 at fs/xfs/libxfs/xfs_bmap.c:4641 xfs_bmapi_convert_delalloc+0xe91/0x1180 fs/xfs/libxfs/xfs_bmap.c:-1
Modules linked in:
CPU: 1 PID: 1221 Comm: kworker/u4:4 Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: writeback wb_workfn (flush-7:0)
RIP: 0010:xfs_bmapi_convert_delalloc+0xe91/0x1180 fs/xfs/libxfs/xfs_bmap.c:4641
Code: e5 23 82 fe 0f 0b e9 c8 f4 ff ff 89 d9 80 e1 07 38 c1 0f 8c f0 f2 ff ff 48 89 df e8 e9 15 cc fe e9 e3 f2 ff ff e8 bf 23 82 fe <0f> 0b 41 bd e4 ff ff ff 48 8b 5c 24 08 e9 62 ff ff ff e8 a8 23 82
RSP: 0018:ffffc90004886a20 EFLAGS: 00010293
RAX: ffffffff82fe7901 RBX: ffffffffffffffff RCX: ffff888022395940
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: ffffffffffffffff
RBP: ffffc90004886c50 R08: ffffffff82fe7317 R09: fffffbfff1c153f6
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffffc90004886b60 R14: ffffc90004886b00 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbb618ee2b8 CR3: 000000002af1a000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
xfs_convert_blocks fs/xfs/xfs_aops.c:245 [inline]
xfs_map_blocks+0xa9e/0x1520 fs/xfs/xfs_aops.c:366
iomap_writepage_map fs/iomap/buffered-io.c:1320 [inline]
iomap_do_writepage+0x63c/0x21c0 fs/iomap/buffered-io.c:1485
write_cache_pages+0xa97/0x1160 mm/page-writeback.c:2277
iomap_writepages+0x64/0x240 fs/iomap/buffered-io.c:1516
xfs_vm_writepages+0x127/0x180 fs/xfs/xfs_aops.c:488
do_writepages+0x481/0x730 mm/page-writeback.c:2386
__writeback_single_inode+0x15b/0xe30 fs/fs-writeback.c:1647
writeback_sb_inodes+0xbce/0x1a40 fs/fs-writeback.c:1930
wb_writeback+0x451/0xc50 fs/fs-writeback.c:2104
wb_do_writeback fs/fs-writeback.c:2247 [inline]
wb_workfn+0x46c/0x1130 fs/fs-writeback.c:2288
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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
Reply all
Reply to author
Forward
0 new messages