From: syzbot <syzbot+62f59a3655c0df0581cd@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [btrfs?] WARNING in btrfs_put_transaction (4)
Date: Thu, 21 Aug 2025 08:16:27 -0700 [thread overview]
Message-ID: <68a7384b.050a0220.3d78fd.002c.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 8f5ae30d69d7 Linux 6.17-rc1
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=13792ba2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c5ac3d8b8abfcb
dashboard link: https://syzkaller.appspot.com/bug?extid=62f59a3655c0df0581cd
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/18a2e4bd0c4a/disk-8f5ae30d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b5395881b25/vmlinux-8f5ae30d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e875f4e3b7ff/Image-8f5ae30d.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+62f59a3655c0df0581cd@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7838 at fs/btrfs/transaction.c:144 btrfs_put_transaction+0x4b8/0x520 fs/btrfs/transaction.c:144
Modules linked in:
CPU: 1 UID: 0 PID: 7838 Comm: btrfs-transacti Not tainted 6.17.0-rc1-syzkaller-g8f5ae30d69d7 #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : btrfs_put_transaction+0x4b8/0x520 fs/btrfs/transaction.c:144
lr : btrfs_put_transaction+0x4b8/0x520 fs/btrfs/transaction.c:144
sp : ffff8000b41a7a70
x29: ffff8000b41a7a80 x28: 1fffe0001f3374a0 x27: dfff800000000000
x26: ffff0000c621a000 x25: dfff800000000000 x24: 1fffe00018c43404
x23: ffff0000c621a000 x22: ffff0000f99b8d38 x21: 0000000000000001
x20: ffff0000c621a358 x19: ffff0000dfc5b2a4 x18: 00000000ffffffff
x17: ffff800093507000 x16: ffff800080535980 x15: 0000000000000001
x14: 1fffe00018c43402 x13: 0000000000000000 x12: 0000000000000000
x11: ffff600018c43403 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000e01edb80 x7 : ffff80008235f5e4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800082358eec
x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000001
Call trace:
btrfs_put_transaction+0x4b8/0x520 fs/btrfs/transaction.c:144 (P)
btrfs_commit_transaction+0x1d24/0x2ce4 fs/btrfs/transaction.c:2583
transaction_kthread+0x200/0x430 fs/btrfs/disk-io.c:1592
kthread+0x5fc/0x75c kernel/kthread.c:463
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:844
irq event stamp: 123680
hardirqs last enabled at (123679): [<ffff80008b028df8>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (123679): [<ffff80008b028df8>] _raw_spin_unlock_irqrestore+0x38/0x98 kernel/locking/spinlock.c:194
hardirqs last disabled at (123680): [<ffff80008b001bfc>] el1_brk64+0x1c/0x48 arch/arm64/kernel/entry-common.c:574
softirqs last enabled at (123658): [<ffff800080201608>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (123656): [<ffff8000802015d4>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
---
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@googlegroups.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
reply other threads:[~2025-08-21 15:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68a7384b.050a0220.3d78fd.002c.GAE@google.com \
--to=syzbot+62f59a3655c0df0581cd@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.