[v6.6] WARNING in btrfs_commit_transaction

3 views
Skip to first unread message

syzbot

unread,
Jun 24, 2025, 2:47:28 PM6/24/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6282921b6825 Linux 6.6.94
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11146f0c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=96da6b2210cda427
dashboard link: https://syzkaller.appspot.com/bug?extid=f98a03ab65ae4389e567
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a3bf0d8e22b2/disk-6282921b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d1d442f782d0/vmlinux-6282921b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8378f4b7e1b/bzImage-6282921b.xz

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

BTRFS critical (device loop2: state M): entry offset 6881280, bytes 1638400, bitmap no
BTRFS info (device loop2: state M): block group has cluster?: no
BTRFS info (device loop2: state M): 0 free space entries at or bigger than 4096 bytes
BTRFS info (device loop2: state M): 3223552 bytes available across all block groups
BTRFS warning (device loop2: state M): Skipping commit of aborted transaction.
------------[ cut here ]------------
BTRFS: Transaction aborted (error -28)
WARNING: CPU: 1 PID: 12054 at fs/btrfs/transaction.c:2004 cleanup_transaction fs/btrfs/transaction.c:2004 [inline]
WARNING: CPU: 1 PID: 12054 at fs/btrfs/transaction.c:2004 btrfs_commit_transaction+0x2ebf/0x3760 fs/btrfs/transaction.c:2587
Modules linked in:
CPU: 1 PID: 12054 Comm: syz.2.2242 Not tainted 6.6.94-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:cleanup_transaction fs/btrfs/transaction.c:2004 [inline]
RIP: 0010:btrfs_commit_transaction+0x2ebf/0x3760 fs/btrfs/transaction.c:2587
Code: e8 d6 d3 0d fe be 01 00 00 00 4c 89 ef e8 b9 a5 a7 00 e9 5a d7 ff ff e8 bf d3 0d fe 48 c7 c7 20 fe ec 8a 89 de e8 b1 38 d8 fd <0f> 0b e9 65 f9 ff ff 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 6f d2
RSP: 0018:ffffc9000562f7c0 EFLAGS: 00010246
RAX: a99fcc9b25b90f00 RBX: 00000000ffffffe4 RCX: 0000000000080000
RDX: ffffc9000d1fa000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: ffffc9000562fae8 R08: ffffc9000562f3c7 R09: 1ffff92000ac5e78
R10: dffffc0000000000 R11: fffff52000ac5e79 R12: ffff88805b859c78
R13: ffff88805b859c98 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007f677922d6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3e7bed CR3: 00000000654e3000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_set_free_space_cache_v1_active+0x71/0x1c0 fs/btrfs/free-space-cache.c:4151
btrfs_remount_cleanup fs/btrfs/super.c:1684 [inline]
btrfs_remount+0x6cc/0x1470 fs/btrfs/super.c:1880
reconfigure_super+0x21e/0x880 fs/super.c:1151
do_remount fs/namespace.c:2900 [inline]
path_mount+0xd19/0xfe0 fs/namespace.c:3685
do_mount fs/namespace.c:3706 [inline]
__do_sys_mount fs/namespace.c:3915 [inline]
__se_sys_mount+0x2da/0x3c0 fs/namespace.c:3892
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f67783900ca
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007f677922ce68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f677922cef0 RCX: 00007f67783900ca
RDX: 0000200000000180 RSI: 0000200000000100 RDI: 0000000000000000
RBP: 0000200000000180 R08: 00007f677922cef0 R09: 00000000001260a9
R10: 00000000001260a9 R11: 0000000000000246 R12: 0000200000000100
R13: 00007f677922ceb0 R14: 0000000000000000 R15: 00002000000001c0
</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
Reply all
Reply to author
Forward
0 new messages