From: syzbot <syzbot+53034ab3f4d670ca496b@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [btrfs?] WARNING in btrfs_add_reserved_bytes
Date: Mon, 25 Sep 2023 11:58:53 -0700 [thread overview]
Message-ID: <000000000000a7db220606338cf7@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 42dc814987c1 Merge tag 'media/v6.6-2' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=153c42d4680000
kernel config: https://syzkaller.appspot.com/x/.config?x=e4ca82a1bedd37e4
dashboard link: https://syzkaller.appspot.com/bug?extid=53034ab3f4d670ca496b
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: https://storage.googleapis.com/syzbot-assets/cb83da482fb0/disk-42dc8149.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7a37cd631377/vmlinux-42dc8149.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d1323cd7f312/bzImage-42dc8149.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+53034ab3f4d670ca496b@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5082 at fs/btrfs/space-info.h:198 btrfs_add_reserved_bytes+0x4b4/0x7b0 fs/btrfs/block-group.c:3694
Modules linked in:
CPU: 1 PID: 5082 Comm: syz-executor.2 Not tainted 6.6.0-rc2-syzkaller-00048-g42dc814987c1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
RIP: 0010:btrfs_space_info_update_bytes_may_use fs/btrfs/space-info.h:198 [inline]
RIP: 0010:btrfs_add_reserved_bytes+0x4b4/0x7b0 fs/btrfs/block-group.c:3694
Code: 5c 24 28 74 08 48 89 df e8 59 ef 32 fe 48 8b 2b 48 89 ef 48 8b 5c 24 30 48 89 de e8 16 89 d8 fd 48 39 dd 73 0b e8 fc 86 d8 fd <0f> 0b 31 ed eb 26 e8 f1 86 d8 fd 48 8b 5c 24 28 48 8b 44 24 40 42
RSP: 0018:ffffc9000421ed70 EFLAGS: 00010293
RAX: ffffffff83b58404 RBX: 0000000000001000 RCX: ffff88801cd80000
RDX: 0000000000000000 RSI: 0000000000001000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff83b583fa R09: 1ffffffff1d34cfd
R10: dffffc0000000000 R11: fffffbfff1d34cfe R12: ffff88807be76800
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000001000
FS: 0000555556b91480(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3123a06d58 CR3: 00000000821cd000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
find_free_extent+0x3aa1/0x5770 fs/btrfs/extent-tree.c:4387
btrfs_reserve_extent+0x422/0x800 fs/btrfs/extent-tree.c:4514
btrfs_alloc_tree_block+0x20e/0x1800 fs/btrfs/extent-tree.c:4929
__btrfs_cow_block+0x465/0x1b00 fs/btrfs/ctree.c:546
btrfs_cow_block+0x403/0x780 fs/btrfs/ctree.c:712
commit_cowonly_roots+0x197/0x860 fs/btrfs/transaction.c:1299
btrfs_commit_transaction+0xff4/0x3720 fs/btrfs/transaction.c:2435
close_ctree+0x3dd/0xd40 fs/btrfs/disk-io.c:4356
generic_shutdown_super+0x13a/0x2c0 fs/super.c:693
kill_anon_super+0x3b/0x70 fs/super.c:1292
btrfs_kill_super+0x41/0x50 fs/btrfs/super.c:2144
deactivate_locked_super+0xa4/0x110 fs/super.c:481
cleanup_mnt+0x426/0x4c0 fs/namespace.c:1254
task_work_run+0x24a/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xd9/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
syscall_exit_to_user_mode+0x64/0x280 kernel/entry/common.c:296
do_syscall_64+0x4d/0xc0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f0019a7de17
Code: b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 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:00007ffc591d0408 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f0019a7de17
RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007ffc591d04c0
RBP: 00007ffc591d04c0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffc591d1580
R13: 00007f0019ac73b9 R14: 00000000001f9f05 R15: 000000000000000d
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2023-09-25 18:58 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=000000000000a7db220606338cf7@google.com \
--to=syzbot+53034ab3f4d670ca496b@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@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.