public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2d6d9df993967dde8297@syzkaller.appspotmail.com>
To: jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
	 linux-kernel@vger.kernel.org, mark@fasheh.com,
	ocfs2-devel@lists.linux.dev,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in _ocfs2_free_suballoc_bits
Date: Wed, 18 Sep 2024 17:04:25 -0700	[thread overview]
Message-ID: <66eb6a89.050a0220.115905.001c.GAE@google.com> (raw)
In-Reply-To: <000000000000b10c48062134870d@google.com>

syzbot has found a reproducer for 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=15caffc7980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=dedbcb1ff4387972
dashboard link: https://syzkaller.appspot.com/bug?extid=2d6d9df993967dde8297
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=158c4b00580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13cffa07980000

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
mounted in repro: https://storage.googleapis.com/syzbot-assets/f1783fdb50b3/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at fs/ocfs2/suballoc.c:2558!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 UID: 0 PID: 6412 Comm: syz-executor137 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 : _ocfs2_free_suballoc_bits+0x8ec/0x1370 fs/ocfs2/suballoc.c:2558
lr : _ocfs2_free_suballoc_bits+0x8ec/0x1370 fs/ocfs2/suballoc.c:2558
sp : ffff80009be27040
x29: ffff80009be271c0 x28: ffff0000dee22c60 x27: dfff800000000000
x26: ffff0000deed4000 x25: 0000000000000000 x24: ffff7000137c4e1c
x23: 0000000000000002 x22: ffff0000def04178 x21: ffff0000def03900
x20: 0000000000000000 x19: ffff0000e2516000 x18: 1fffe000366d79ee
x17: ffff80008f56d000 x16: ffff800083032784 x15: 0000000000000001
x14: 1ffff000137c4dac x13: 0000000000000000 x12: ffff80009be26f40
x11: ffff8000820904b8 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000d97ddac0 x7 : ffff80008201e048 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : ffff0000deed4000 x1 : 0000000000000000 x0 : 0000000000000002
Call trace:
 _ocfs2_free_suballoc_bits+0x8ec/0x1370 fs/ocfs2/suballoc.c:2558
 ocfs2_free_suballoc_bits fs/ocfs2/suballoc.c:2598 [inline]
 ocfs2_free_dinode+0xb0/0xe8 fs/ocfs2/suballoc.c:2613
 ocfs2_remove_inode fs/ocfs2/inode.c:696 [inline]
 ocfs2_wipe_inode fs/ocfs2/inode.c:818 [inline]
 ocfs2_delete_inode fs/ocfs2/inode.c:1079 [inline]
 ocfs2_evict_inode+0x281c/0x468c fs/ocfs2/inode.c:1216
 evict+0x418/0x894 fs/inode.c:704
 iput_final fs/inode.c:1838 [inline]
 iput+0x74c/0x830 fs/inode.c:1864
 d_delete_notify include/linux/fsnotify.h:332 [inline]
 vfs_rmdir+0x35c/0x468 fs/namei.c:4306
 do_rmdir+0x2e0/0x720 fs/namei.c:4352
 __do_sys_unlinkat fs/namei.c:4528 [inline]
 __se_sys_unlinkat fs/namei.c:4522 [inline]
 __arm64_sys_unlinkat+0xdc/0xf8 fs/namei.c:4522
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712
 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730
 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598
Code: 97932c46 f9400ffc 17fffe2a 97932c43 (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.

      parent reply	other threads:[~2024-09-19  0:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 10:29 [syzbot] [ocfs2?] kernel BUG in _ocfs2_free_suballoc_bits syzbot
2024-09-09 18:22 ` syzbot
2024-09-19  0:04 ` syzbot [this message]

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=66eb6a89.050a0220.115905.001c.GAE@google.com \
    --to=syzbot+2d6d9df993967dde8297@syzkaller.appspotmail.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --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