From: syzbot <syzbot+f446972e621930b149d8@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_remove_qgroup
Date: Thu, 03 Oct 2024 17:07:24 -0700 [thread overview]
Message-ID: <66ff31bc.050a0220.49194.03ee.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 5f5673607153 Merge branch 'for-next/core' into for-kernelci
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=14444127980000
kernel config: https://syzkaller.appspot.com/x/.config?x=dedbcb1ff4387972
dashboard link: https://syzkaller.appspot.com/bug?extid=f446972e621930b149d8
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/40172aed5414/disk-5f567360.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/58372f305e9d/vmlinux-5f567360.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d2aae6fa798f/Image-5f567360.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f446972e621930b149d8@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7433 at fs/btrfs/qgroup.c:1855 btrfs_remove_qgroup+0xab0/0xd60 fs/btrfs/qgroup.c:1856
Modules linked in:
CPU: 1 UID: 0 PID: 7433 Comm: btrfs-cleaner Not tainted 6.11.0-rc7-syzkaller-g5f5673607153 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : btrfs_remove_qgroup+0xab0/0xd60 fs/btrfs/qgroup.c:1856
lr : btrfs_remove_qgroup+0x854/0xd60 fs/btrfs/qgroup.c:1854
sp : ffff8000a3797a20
x29: ffff8000a3797b40 x28: ffff0000da08d800 x27: ffff0000da08d7f0
x26: 0000000000000000 x25: dfff800000000000 x24: 1fffe0001b411afe
x23: ffffffffffff0000 x22: ffff0000ed8738b8 x21: 0000000000000100
x20: ffff0000da08c000 x19: ffff7000146f2f50 x18: ffff8000a3797700
x17: 000000000003c15e x16: ffff8000803600cc x15: ffff7000146f2f2c
x14: 1ffff000146f2f2c x13: 0000000000000004 x12: ffffffffffffffff
x11: ffff7000146f2f2c x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000ef1b3c80 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000020 x4 : 0000000000000000 x3 : ffff8000803601f4
x2 : 0000000000000001 x1 : ffff80008ec0334d x0 : ffff80008fcb3300
Call trace:
btrfs_remove_qgroup+0xab0/0xd60 fs/btrfs/qgroup.c:1856
btrfs_qgroup_cleanup_dropped_subvolume+0x158/0x194 fs/btrfs/qgroup.c:1904
btrfs_drop_snapshot+0x2a0/0x1be4 fs/btrfs/extent-tree.c:6260
btrfs_clean_one_deleted_snapshot+0x238/0x32c
cleaner_kthread+0x208/0x3dc fs/btrfs/disk-io.c:1520
kthread+0x288/0x310 kernel/kthread.c:389
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
irq event stamp: 6130
hardirqs last enabled at (6129): [<ffff800080a88010>] kasan_quarantine_put+0x1a0/0x1c8 mm/kasan/quarantine.c:234
hardirqs last disabled at (6130): [<ffff80008b3363f4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:470
softirqs last enabled at (5920): [<ffff8000800307f8>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (5918): [<ffff8000800307c4>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
BTRFS warning (device loop3): to be deleted qgroup 0/256 has non-zero numbers, rfer 18446744073709486080 rfer_cmpr 18446744073709486080 excl 0 excl_cmpr 0
---
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:[~2024-10-04 0:07 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=66ff31bc.050a0220.49194.03ee.GAE@google.com \
--to=syzbot+f446972e621930b149d8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).