[v6.1] kernel BUG in close_ctree (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0cbb5f65e52f Linux 6.1.128
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14b3afdf980000
kernel config: https://syzkaller.appspot.com/x/.config?x=abb6e3847403ee03
dashboard link: https://syzkaller.appspot.com/bug?extid=1bb366f0586d485d68d5
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fc67b93cdf77/disk-0cbb5f65.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/833d6a619b95/vmlinux-0cbb5f65.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2f8b026bdbd9/Image-0cbb5f65.gz.xz

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

BTRFS info (device loop0): last unmount of filesystem ed167579-eb65-4e76-9a50-61ac97e9b59d
BTRFS warning (device loop0): transaction 14 (with 0 dirty metadata bytes) is not committed
assertion failed: !found, in fs/btrfs/disk-io.c:4584
------------[ cut here ]------------
kernel BUG at fs/btrfs/ctree.h:3722!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4301 Comm: syz-executor Not tainted 6.1.128-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : assertfail+0x28/0x2c fs/btrfs/ctree.h:3721
lr : assertfail+0x28/0x2c fs/btrfs/ctree.h:3721
sp : ffff800021247710
x29: ffff800021247710 x28: ffff0000de71a028 x27: dfff800000000000
x26: ffff0000de71a000 x25: 1ffff00004248ef8 x24: ffff8000212477e0
x23: ffff8000212477c0 x22: 1ffff00004248efc x21: ffff0000db0b8ce8
x20: ffff8000212477a0 x19: ffff0000db0b8000 x18: 1fffe00036798976
x17: ffff800015aed000 x16: ffff80001231f9fc x15: ffff0001b3cc4bbc
x14: 1ffff00002b5e0b2 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : c577508e6f93f300
x8 : c577508e6f93f300 x7 : ffff8000082783ec x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff80000ab302f8
x2 : ffff0001b3cc4cd0 x1 : 0000000100000000 x0 : 0000000000000034
Call trace:
assertfail+0x28/0x2c fs/btrfs/ctree.h:3721
warn_about_uncommitted_trans fs/btrfs/disk-io.c:4584 [inline]
close_ctree+0xa70/0xb10 fs/btrfs/disk-io.c:4760
btrfs_put_super+0x70/0x80 fs/btrfs/super.c:397
generic_shutdown_super+0x130/0x328 fs/super.c:501
kill_anon_super+0x4c/0x74 fs/super.c:1128
btrfs_kill_super+0x40/0x58 fs/btrfs/super.c:2449
deactivate_locked_super+0xac/0x124 fs/super.c:332
deactivate_super+0xf0/0x110 fs/super.c:363
cleanup_mnt+0x394/0x41c fs/namespace.c:1186
__cleanup_mnt+0x20/0x30 fs/namespace.c:1193
task_work_run+0x240/0x2f0 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
do_notify_resume+0x2080/0x2cb8 arch/arm64/kernel/signal.c:1132
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x9c/0x168 arch/arm64/kernel/entry-common.c:638
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: 91048000 90002c22 91100042 97fff91d (d4210000)
---[ 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 syzk...@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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: da3c5173c55f Linux 6.1.140
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=113f5ad4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2bfe5a2f04bb30e3
dashboard link: https://syzkaller.appspot.com/bug?extid=1bb366f0586d485d68d5
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=124b28e8580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2c3ee4de68a1/disk-da3c5173.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/19742d73f52b/vmlinux-da3c5173.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0ffdd39d32ee/Image-da3c5173.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/76f5dee5f342/mount_1.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=144b28e8580000)

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

BTRFS warning (device loop0): transaction 15 (with 0 dirty metadata bytes) is not committed

assertion failed: !found, in fs/btrfs/disk-io.c:4584
------------[ cut here ]------------
kernel BUG at fs/btrfs/ctree.h:3722!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:

CPU: 1 PID: 4407 Comm: syz-executor Not tainted 6.1.140-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025

pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : assertfail+0x28/0x2c fs/btrfs/ctree.h:3721
lr : assertfail+0x28/0x2c fs/btrfs/ctree.h:3721

sp : ffff800020cf77d0
x29: ffff800020cf77d0 x28: ffff800020cf7800 x27: dfff800000000000
x26: ffff0000d82ec540 x25: 1fffe0001b05d8a8 x24: ffff0000d5fda000
x23: ffff0000d5fda028 x22: ffff0000d82ecce8 x21: ffff0000d82ecce8
x20: ffff0000d82ecce8 x19: ffff0000d82ec000 x18: ffff800011a7bd00
x17: 1fffe00033ee7176 x16: ffff8000082d1c1c x15: 0000000040000000
x14: 0000000000000002 x13: 1ffff00002a0e0b1 x12: 0000000000ff0100
x11: ff008000083098d0 x10: 0000000000000000 x9 : a1feadde584d8e00
x8 : a1feadde584d8e00 x7 : ffff8000082516f8 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff80000a83bd8c
x2 : ffff00019f738cd0 x1 : 0000000100000000 x0 : 0000000000000034

Call trace:
assertfail+0x28/0x2c fs/btrfs/ctree.h:3721
warn_about_uncommitted_trans fs/btrfs/disk-io.c:4584 [inline]

close_ctree+0x9a8/0xa64 fs/btrfs/disk-io.c:4772
btrfs_put_super+0x70/0x80 fs/btrfs/super.c:397
generic_shutdown_super+0x130/0x324 fs/super.c:501
kill_anon_super+0x4c/0x80 fs/super.c:1128
btrfs_kill_super+0x40/0x58 fs/btrfs/super.c:2448
deactivate_locked_super+0xac/0x124 fs/super.c:332
deactivate_super+0xe8/0x108 fs/super.c:363
cleanup_mnt+0x37c/0x404 fs/namespace.c:1186
__cleanup_mnt+0x20/0x30 fs/namespace.c:1193
task_work_run+0x1ec/0x270 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
do_notify_resume+0x1f70/0x2b0c arch/arm64/kernel/signal.c:1137

prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]

el0_svc+0x98/0x138 arch/arm64/kernel/entry-common.c:638

el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Code: 91178000 90003122 91230042 97ff981f (d4210000)

---[ end trace 0000000000000000 ]---


---

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.