[v5.15] WARNING in btrfs_put_transaction

0 views
Skip to first unread message

syzbot

unread,
Jul 11, 2023, 11:58:07 AM7/11/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11b3a0a2a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c67dae6b27f0d6cd
dashboard link: https://syzkaller.appspot.com/bug?extid=633e55c00c82ceea30f6
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4aa2cbf1e81c/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2ebee78b098c/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4e17f9ac4b6a/bzImage-d54cfc42.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 3542 at fs/btrfs/transaction.c:131 btrfs_put_transaction+0x37b/0x3e0
Modules linked in:
CPU: 1 PID: 3542 Comm: syz-executor.1 Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
RIP: 0010:btrfs_put_transaction+0x37b/0x3e0 fs/btrfs/transaction.c:130
Code: 48 89 da e8 4a b4 bd 06 e9 00 fe ff ff e8 2d 1f 23 fe 0f 0b e9 ef fc ff ff e8 21 1f 23 fe 0f 0b e9 72 fd ff ff e8 15 1f 23 fe <0f> 0b e9 9b fd ff ff e8 09 1f 23 fe 48 89 df be 03 00 00 00 48 83
RSP: 0018:ffffc90002e2fa00 EFLAGS: 00010293
RAX: ffffffff835ce18b RBX: ffff888049d16340 RCX: ffff8880237ed940
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: 0000000000000001 R08: ffffffff835cde8b R09: ffffed10093a2c03
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888075878cb8 R14: ffff888049d16000 R15: ffff888075878be8
FS: 00005555564b2480(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fecfca85198 CR3: 000000004bcbf000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_cleanup_transaction+0x53d/0x1d20 fs/btrfs/disk-io.c:5041
btrfs_error_commit_super fs/btrfs/disk-io.c:4609 [inline]
close_ctree+0x468/0x886 fs/btrfs/disk-io.c:4447
generic_shutdown_super+0x136/0x2c0 fs/super.c:475
kill_anon_super+0x37/0x60 fs/super.c:1067
btrfs_kill_super+0x3d/0x50 fs/btrfs/super.c:2391
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f93abc44e57
Code: b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b0 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007fff5355a418 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f93abc44e57
RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007fff5355a4d0
RBP: 00007fff5355a4d0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fff5355b590
R13: 00007f93abc8e3b9 R14: 0000000000031797 R15: 000000000000000f
</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 change 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

syzbot

unread,
Jul 11, 2023, 5:46:06 PM7/11/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1505cd8ca80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c67dae6b27f0d6cd
dashboard link: https://syzkaller.appspot.com/bug?extid=633e55c00c82ceea30f6
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=115cf1d4a80000
mounted in repro: https://storage.googleapis.com/syzbot-assets/19d521e91fa8/mount_1.gz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 3545 at fs/btrfs/transaction.c:131 btrfs_put_transaction+0x37b/0x3e0
Modules linked in:
CPU: 0 PID: 3545 Comm: syz-executor.2 Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
RIP: 0010:btrfs_put_transaction+0x37b/0x3e0 fs/btrfs/transaction.c:130
Code: 48 89 da e8 4a b4 bd 06 e9 00 fe ff ff e8 2d 1f 23 fe 0f 0b e9 ef fc ff ff e8 21 1f 23 fe 0f 0b e9 72 fd ff ff e8 15 1f 23 fe <0f> 0b e9 9b fd ff ff e8 09 1f 23 fe 48 89 df be 03 00 00 00 48 83
RSP: 0018:ffffc9000314fa00 EFLAGS: 00010293
RAX: ffffffff835ce18b RBX: ffff8880740d3340 RCX: ffff888078975940
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: 0000000000000001 R08: ffffffff835cde8b R09: ffffed100e81a603
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888063bd4cb8 R14: ffff8880740d3000 R15: ffff888063bd4be8
FS: 0000555556572480(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4d51dde000 CR3: 00000000204b3000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_cleanup_transaction+0x53d/0x1d20 fs/btrfs/disk-io.c:5041
btrfs_error_commit_super fs/btrfs/disk-io.c:4609 [inline]
close_ctree+0x468/0x886 fs/btrfs/disk-io.c:4447
generic_shutdown_super+0x136/0x2c0 fs/super.c:475
kill_anon_super+0x37/0x60 fs/super.c:1067
btrfs_kill_super+0x3d/0x50 fs/btrfs/super.c:2391
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1d2482de57
Code: b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b0 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffe018812b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f1d2482de57
RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007ffe01881370
RBP: 00007ffe01881370 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffe01882430
R13: 00007f1d248773b9 R14: 000000000004c500 R15: 000000000000000d
</TASK>


---
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.
Reply all
Reply to author
Forward
0 new messages