Hello,
syzbot found the following issue on:
HEAD commit: 082280fe94a0 Linux 6.1.57
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=121775b5680000
kernel config:
https://syzkaller.appspot.com/x/.config?x=2fcfda4f62e1716c
dashboard link:
https://syzkaller.appspot.com/bug?extid=3b29376a259c4c012cc0
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/13811dd7bcb9/disk-082280fe.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/78b9e829ec6f/vmlinux-082280fe.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/2d5fc66b2352/bzImage-082280fe.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+3b2937...@syzkaller.appspotmail.com
BTRFS info (device loop0: state M): using default commit interval 30s
BTRFS info (device loop0: state M): force clearing of disk cache
BTRFS warning (device loop0: state M): Skipping commit of aborted transaction.
------------[ cut here ]------------
WARNING: CPU: 1 PID: 31506 at fs/btrfs/transaction.c:1992 cleanup_transaction fs/btrfs/transaction.c:1992 [inline]
WARNING: CPU: 1 PID: 31506 at fs/btrfs/transaction.c:1992 btrfs_commit_transaction+0x33b4/0x3c70 fs/btrfs/transaction.c:2578
Modules linked in:
CPU: 1 PID: 31506 Comm: syz-executor.0 Not tainted 6.1.57-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
RIP: 0010:cleanup_transaction fs/btrfs/transaction.c:1992 [inline]
RIP: 0010:btrfs_commit_transaction+0x33b4/0x3c70 fs/btrfs/transaction.c:2578
Code: 89 e7 e8 0f bc af 00 e9 24 d3 ff ff e8 e5 29 03 fe e9 fe fe ff ff e8 db 29 03 fe 48 c7 c7 c0 97 2d 8b 8b 34 24 e8 fc 23 cb fd <0f> 0b e9 a8 f8 ff ff e8 c0 29 03 fe e9 be fe ff ff 89 d9 80 e1 07
RSP: 0018:ffffc900172c7780 EFLAGS: 00010246
RAX: 3141dec4ce533100 RBX: ffff888084640001 RCX: 0000000000040000
RDX: ffffc90003a91000 RSI: 000000000000e8c3 RDI: 000000000000e8c4
RBP: ffffc900172c7ac0 R08: ffffffff81526dae R09: fffff52002e58e51
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888025c8cde8
R13: dffffc0000000000 R14: 0000000000000000 R15: 1ffff1101232dd82
FS: 00007f0b9e78c6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3312c000 CR3: 0000000035812000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_set_free_space_cache_v1_active+0x6d/0x230 fs/btrfs/free-space-cache.c:4135
btrfs_remount_cleanup fs/btrfs/super.c:1990 [inline]
btrfs_remount+0x72b/0x1510 fs/btrfs/super.c:2180
reconfigure_super+0x43a/0x870 fs/super.c:966
do_remount fs/namespace.c:2702 [inline]
path_mount+0xe69/0x1090 fs/namespace.c:3362
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f0b9da7cae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0b9e78c0c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f0b9db9bf80 RCX: 00007f0b9da7cae9
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000000000000
RBP: 00007f0b9dac847a R08: 0000000020000000 R09: 0000000000000000
R10: 00000000032d6074 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f0b9db9bf80 R15: 00007ffe91df9d08
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup