[btrfs?] WARNING in cleanup_transaction

5 views
Skip to first unread message

syzbot

unread,
Dec 19, 2022, 6:57:34 AM12/19/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c4215ee4771b Linux 4.14.302
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=130ab6bf880000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a9988fe055c9527
dashboard link: https://syzkaller.appspot.com/bug?extid=0a4d82ba149f8f01efc8
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=104ab82b880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13ba58f7880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c93ba055d204/disk-c4215ee4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfbc929a33c1/vmlinux-c4215ee4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/444658051770/bzImage-c4215ee4.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/a94a57b639bd/mount_0.gz

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

RBP: 00007ffc292fd500 R08: 0000000000000002 R09: 00007fb385003231
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000006
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
BTRFS warning (device loop0): Skipping commit of aborted transaction.
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7992 at fs/btrfs/transaction.c:1883 cleanup_transaction.cold+0x14/0x7ab fs/btrfs/transaction.c:1883
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 7992 Comm: syz-executor282 Not tainted 4.14.302-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:967
RIP: 0010:cleanup_transaction.cold+0x14/0x7ab fs/btrfs/transaction.c:1883
RSP: 0018:ffff8880912cf6d0 EFLAGS: 00010282
RAX: 0000000000000026 RBX: ffff88809655c680 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff87cd1200 RDI: ffffed1012259ed0
RBP: ffff88808dfb08a0 R08: 0000000000000026 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 1ffff11012259ee1
R13: 00000000fffffff4 R14: ffff88808dfb0900 R15: ffff88808dfb08d0
btrfs_commit_transaction+0x1735/0x2210 fs/btrfs/transaction.c:2341
create_snapshot fs/btrfs/ioctl.c:749 [inline]
btrfs_mksubvol+0xce9/0x1000 fs/btrfs/ioctl.c:892
btrfs_ioctl_snap_create_transid+0x38e/0x420 fs/btrfs/ioctl.c:1699
btrfs_ioctl_snap_create_v2+0x22f/0x340 fs/btrfs/ioctl.c:1774
btrfs_ioctl+0x1824/0x5b20 fs/btrfs/ioctl.c:5614
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7fb385880db9
RSP: 002b:00007ffc292fd4f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007fb385880db9
RDX: 0000000020001a80 RSI: 0000000050009417 RDI: 0000000000000004
RBP: 00007ffc292fd500 R08: 0000000000000002 R09: 00007fb385003231
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000006
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages