linux-kernel - [syzbot] [btrfs?] WARNING in btrfs_put

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <67433bfd.050a0220.1cc393.0042.GAE@google.com>
Date: Sun, 24 Nov 2024 06:45:17 -0800
From: syzbot <syzbot+d6ba71ce7a916cf10094@...kaller.appspotmail.com>
To: clm@...com, dsterba@...e.com, josef@...icpanda.com, 
	linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [btrfs?] WARNING in btrfs_put_transaction (3)

Hello,

syzbot found the following issue on:

HEAD commit:    bf9aa14fc523 Merge tag 'timers-core-2024-11-18' of git://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1050cae8580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=48190c1cdf985419
dashboard link: https://syzkaller.appspot.com/bug?extid=d6ba71ce7a916cf10094
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 (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-bf9aa14f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a86e66fb23d0/vmlinux-bf9aa14f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fccf5aa8139f/bzImage-bf9aa14f.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5346 at fs/btrfs/transaction.c:144 btrfs_put_transaction+0x356/0x3c0 fs/btrfs/transaction.c:144
Modules linked in:
CPU: 0 UID: 0 PID: 5346 Comm: btrfs-transacti Not tainted 6.12.0-syzkaller-01782-gbf9aa14fc523 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:btrfs_put_transaction+0x356/0x3c0 fs/btrfs/transaction.c:144
Code: 89 da e8 0d c5 10 08 48 bd 00 00 00 00 00 fc ff df e9 02 fe ff ff e8 09 12 de fd 90 0f 0b 90 e9 0d fd ff ff e8 fb 11 de fd 90 <0f> 0b 90 e9 84 fd ff ff e8 ed 11 de fd 90 0f 0b 90 e9 a1 fd ff ff
RSP: 0018:ffffc9000d2f7b40 EFLAGS: 00010293
RAX: ffffffff83b6d7e5 RBX: ffff88804d306358 RCX: ffff888000728000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: dffffc0000000000 R08: ffffffff83b6d50f R09: 1ffff11009a60c02
R10: dffffc0000000000 R11: ffffed1009a60c03 R12: ffff88804d306028
R13: ffffc9000d2f7d40 R14: ffff88804d306000 R15: ffff888043e54bf8
FS:  0000000000000000(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff3827ffb0 CR3: 00000000458e4000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 btrfs_cleanup_transaction+0x562/0x1ca0 fs/btrfs/disk-io.c:4805
 transaction_kthread+0x307/0x500 fs/btrfs/disk-io.c:1610
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </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 syzkaller@...glegroups.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