All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+48ed002119c0f19daf63@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_release_global_block_rsv (2)
Date: Tue, 19 Nov 2024 18:12:31 -0800	[thread overview]
Message-ID: <673d458f.050a0220.363a1b.0003.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    f868cd251776 Merge tag 'drm-fixes-2024-11-16' of https://g..
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=12dc1b5f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1503500c6f615d24
dashboard link: https://syzkaller.appspot.com/bug?extid=48ed002119c0f19daf63
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11dfd130580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15dfd130580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/66a42ffd702c/disk-f868cd25.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b0bd620eb146/vmlinux-f868cd25.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6d14a828c8cb/bzImage-f868cd25.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/28ab3d88b5f1/mount_0.gz
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/f64e4ef84354/mount_1.gz

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

BTRFS info (device loop1): last unmount of filesystem b65e5074-7275-4634-a025-a4403a9281c2
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5830 at fs/btrfs/block-rsv.c:459 btrfs_release_global_block_rsv+0x261/0x270 fs/btrfs/block-rsv.c:459
Modules linked in:
CPU: 1 UID: 0 PID: 5830 Comm: syz-executor323 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
RIP: 0010:btrfs_release_global_block_rsv+0x261/0x270 fs/btrfs/block-rsv.c:459
Code: 0f 0b 90 e9 0c ff ff ff e8 2c 0d bd fd 90 0f 0b 90 e9 36 ff ff ff e8 1e 0d bd fd 90 0f 0b 90 e9 67 ff ff ff e8 10 0d bd fd 90 <0f> 0b 90 eb 89 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90
RSP: 0018:ffffc90003baf9b8 EFLAGS: 00010293
RAX: ffffffff83d7dca0 RBX: ffffffffffff0000 RCX: ffff888035a31e00
RDX: 0000000000000000 RSI: ffffffffffff0000 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffff83d7dc25 R09: 1ffff1100540de01
R10: dffffc0000000000 R11: ffffed100540de02 R12: ffff88802a06a000
R13: 1ffff1100540d42e R14: ffff8880336f4400 R15: dffffc0000000000
FS:  000055558bffa3c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb775400000 CR3: 000000007e426000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 btrfs_free_block_groups+0xc3c/0x1080 fs/btrfs/block-group.c:4472
 close_ctree+0x772/0xd60 fs/btrfs/disk-io.c:4378
 generic_shutdown_super+0x139/0x2d0 fs/super.c:642
 kill_anon_super+0x3b/0x70 fs/super.c:1237
 btrfs_kill_super+0x41/0x50 fs/btrfs/super.c:2114
 deactivate_locked_super+0xc4/0x130 fs/super.c:473
 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373
 task_work_run+0x24f/0x310 kernel/task_work.c:239
 ptrace_notify+0x2d2/0x380 kernel/signal.c:2404
 ptrace_report_syscall include/linux/ptrace.h:415 [inline]
 ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline]
 syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173
 syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline]
 syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218
 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb77d64c1e7
Code: 08 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 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:00007ffe158a5b88 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fb77d64c1e7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffe158a5c40
RBP: 00007ffe158a5c40 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000206 R12: 00007ffe158a6cf0
R13: 000055558bffb700 R14: 431bde82d7b634db R15: 00007ffe158a6c94
 </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@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 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.

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:[~2024-11-20  2:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20  2:12 syzbot [this message]
2025-10-15 16:18 ` [syzbot] [btrfs?] WARNING in btrfs_release_global_block_rsv (2) syzbot

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=673d458f.050a0220.363a1b.0003.GAE@google.com \
    --to=syzbot+48ed002119c0f19daf63@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.