From: syzbot <syzbot+a306f914b4d01b3958fe@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] kernel BUG in btrfs_free_tree_block
Date: Mon, 26 Sep 2022 10:49:41 -0700 [thread overview]
Message-ID: <000000000000fcba1e05e998263c@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: c194837ebb57 Merge branch 'for-next/core', remote-tracking..
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=1664ce88880000
kernel config: https://syzkaller.appspot.com/x/.config?x=15a770deac0c935a
dashboard link: https://syzkaller.appspot.com/bug?extid=a306f914b4d01b3958fe
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=112dc2a8880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=112cb7f8880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8d8ae425e7fa/disk-c194837e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c540d501ebe7/vmlinux-c194837e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a306f914b4d01b3958fe@syzkaller.appspotmail.com
BTRFS info (device loop0): using crc32c (crc32c-generic) checksum algorithm
BTRFS info (device loop0): using free space tree
BTRFS info (device loop0): enabling ssd optimizations
------------[ cut here ]------------
kernel BUG at fs/btrfs/extent-tree.c:3273!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 3114 Comm: syz-executor276 Not tainted 6.0.0-rc6-syzkaller-17742-gc194837ebb57 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : btrfs_free_tree_block+0x400/0x43c fs/btrfs/extent-tree.c:3273
lr : btrfs_free_tree_block+0x400/0x43c fs/btrfs/extent-tree.c:3273
sp : ffff800012743670
x29: ffff8000127436c0 x28: 0000000000503000 x27: 0000000000000002
x26: ffff80000cf00000 x25: ffff0000cc66c000 x24: fffffc0000000000
x23: 00000000fffffff4 x22: 0000000000000001 x21: ffff0000ca5b7000
x20: 0000000000000000 x19: ffff0000c9478d80 x18: fffffffffffffff5
x17: 0000000000000000 x16: ffff80000db49158 x15: ffff0000c8a2cf80
x14: 0000000000000010 x13: 0000000000000000 x12: ffff0000c8a2cf80
x11: ff808000090f8124 x10: 0000000000000000 x9 : ffff8000090f8124
x8 : ffff0000c8a2cf80 x7 : ffff8000084b1e88 x6 : 0000000000000000
x5 : 0000000000000c40 x4 : 0000000000000068 x3 : 0000000000000068
x2 : ffff0000c3461800 x1 : 00000000fffffff4 x0 : 0000000000000000
Call trace:
btrfs_free_tree_block+0x400/0x43c fs/btrfs/extent-tree.c:3273
__btrfs_cow_block+0x688/0xa88 fs/btrfs/ctree.c:467
btrfs_cow_block+0x1d0/0x258 fs/btrfs/ctree.c:572
btrfs_search_slot+0x458/0xfd8
btrfs_insert_empty_items+0x4c/0xd0 fs/btrfs/ctree.c:4069
btrfs_create_new_inode+0x610/0xd18 fs/btrfs/inode.c:6428
btrfs_create_common+0x114/0x1b4 fs/btrfs/inode.c:6657
btrfs_create+0x8c/0xb0 fs/btrfs/inode.c:6697
lookup_open fs/namei.c:3413 [inline]
open_last_lookups fs/namei.c:3481 [inline]
path_openat+0x804/0x11c4 fs/namei.c:3688
do_filp_open+0xdc/0x1b8 fs/namei.c:3718
do_sys_openat2+0xb8/0x22c fs/open.c:1311
do_sys_open fs/open.c:1327 [inline]
__do_sys_openat fs/open.c:1343 [inline]
__se_sys_openat fs/open.c:1338 [inline]
__arm64_sys_openat+0xb0/0xe0 fs/open.c:1338
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:636
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:654
el0t_64_sync+0x18c/0x190
Code: 94bb0eb0 97c6a0e9 d4210000 97c6a0e7 (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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2022-09-26 18:05 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=000000000000fcba1e05e998263c@google.com \
--to=syzbot+a306f914b4d01b3958fe@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.