WARNING in cleanup_transaction (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=126e8647880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=256cfdd2e21328f9182e
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

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

BTRFS error (device loop5): tree block 5259264 owner 256 already locked by pid=25896, extent tree corruption detected
BTRFS warning (device loop5): Skipping commit of aborted transaction.
------------[ cut here ]------------
WARNING: CPU: 1 PID: 25896 at fs/btrfs/transaction.c:1872 cleanup_transaction+0x1bf/0x250 fs/btrfs/transaction.c:1872
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 25896 Comm: syz-executor.5 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:cleanup_transaction+0x1bf/0x250 fs/btrfs/transaction.c:1872
Code: 89 e6 bf fb ff ff ff e8 5f ed 7b fe 41 83 fc fb 0f 84 d5 b9 13 05 e8 e0 eb 7b fe 44 89 e6 48 c7 c7 80 af a4 88 e8 b6 23 0c 05 <0f> 0b e8 ca eb 7b fe 44 89 e1 ba 50 07 00 00 48 89 ef 48 c7 c6 a0
RSP: 0018:ffff8880a0ecf320 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 1ffff110141d9e6b RCX: 0000000000000000
RDX: 0000000000040000 RSI: ffffffff814dff01 RDI: ffffed10141d9e56
RBP: ffff8880482bfb28 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 00000000ffffff8b
R13: ffff8880482bfb78 R14: ffff8880482bfb48 R15: 0000000000000000
btrfs_commit_transaction+0x1de7/0x2480 fs/btrfs/transaction.c:2338
create_subvol+0x10a3/0x1850 fs/btrfs/ioctl.c:753
btrfs_mksubvol+0xe1d/0x1160 fs/btrfs/ioctl.c:1007
btrfs_ioctl_snap_create_transid+0x2a7/0x430 fs/btrfs/ioctl.c:1771
btrfs_ioctl_snap_create_v2+0x2db/0x5d0 fs/btrfs/ioctl.c:1885
btrfs_ioctl+0x26f6/0x76d0 fs/btrfs/ioctl.c:5934
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f6200d720d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f61ff2e4168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f6200e91f80 RCX: 00007f6200d720d9
RDX: 0000000020000a80 RSI: 0000000050009418 RDI: 0000000000000004
RBP: 00007f61ff2e41d0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007ffdac622cbf R14: 00007f61ff2e4300 R15: 0000000000022000
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y

console output: https://syzkaller.appspot.com/x/log.txt?x=12ee5c47880000

kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=256cfdd2e21328f9182e
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14b89247880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=144626d5880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/39dc61aef972/mount_0.gz

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

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 00007ffcc221da50 R14: 0000000000000003 R15: 00007ffcc221da4a
BTRFS error (device loop0): tree block 5259264 owner 256 already locked by pid=8106, extent tree corruption detected
BTRFS warning (device loop0): Skipping commit of aborted transaction.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8106 at fs/btrfs/transaction.c:1872 cleanup_transaction+0x1bf/0x250 fs/btrfs/transaction.c:1872

Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 8106 Comm: syz-executor720 Not tainted 4.19.211-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:cleanup_transaction+0x1bf/0x250 fs/btrfs/transaction.c:1872
Code: 89 e6 bf fb ff ff ff e8 5f ed 7b fe 41 83 fc fb 0f 84 d5 b9 13 05 e8 e0 eb 7b fe 44 89 e6 48 c7 c7 80 af a4 88 e8 b6 23 0c 05 <0f> 0b e8 ca eb 7b fe 44 89 e1 ba 50 07 00 00 48 89 ef 48 c7 c6 a0

RSP: 0018:ffff888094c7f320 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 1ffff1101298fe6b RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed101298fe56
RBP: ffff88808ac38e70 R08: 0000000000000001 R09: 0000000000000000

R10: 0000000000000005 R11: 0000000000000000 R12: 00000000ffffff8b

R13: ffff88808ac38ec0 R14: ffff88808ac38e90 R15: 0000000000000000

btrfs_commit_transaction+0x1de7/0x2480 fs/btrfs/transaction.c:2338
create_subvol+0x10a3/0x1850 fs/btrfs/ioctl.c:753
btrfs_mksubvol+0xe1d/0x1160 fs/btrfs/ioctl.c:1007
btrfs_ioctl_snap_create_transid+0x2a7/0x430 fs/btrfs/ioctl.c:1771
btrfs_ioctl_snap_create_v2+0x2db/0x5d0 fs/btrfs/ioctl.c:1885
btrfs_ioctl+0x26f6/0x76d0 fs/btrfs/ioctl.c:5934
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe

RIP: 0033:0x7f17198042b9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 14 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcc221da18 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f17198042b9

RDX: 0000000020000a80 RSI: 0000000050009418 RDI: 0000000000000004

RBP: 0000000000000005 R08: 0000000000000002 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 00007ffcc221da50 R14: 0000000000000003 R15: 00007ffcc221da4a