All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f8bc4176e51e87e0928f@syzkaller.appspotmail.com>
To: agruenba@redhat.com, cluster-devel@redhat.com,
	linux-kernel@vger.kernel.org, rpeterso@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in gfs2_ri_update
Date: Thu, 15 Sep 2022 23:06:34 -0700	[thread overview]
Message-ID: <000000000000075fb105e8c52ada@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    a6b443748715 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=10340c9f080000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e79d82586727c5df
dashboard link: https://syzkaller.appspot.com/bug?extid=f8bc4176e51e87e0928f
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

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1436897f0dc0/disk-a6b44374.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/68c4de151fbb/vmlinux-a6b44374.xz

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

gfs2: fsid=syz:syz.0: first mount done, others may mount
------------[ cut here ]------------
WARNING: CPU: 1 PID: 2396 at mm/page_alloc.c:5491 __alloc_pages+0x150/0x1fc mm/page_alloc.c:5491
Modules linked in:
CPU: 1 PID: 2396 Comm: syz-executor.3 Not tainted 6.0.0-rc4-syzkaller-17255-ga6b443748715 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __alloc_pages+0x150/0x1fc mm/page_alloc.c:5491
lr : alloc_pages+0x374/0x484
sp : ffff8000148f3790
x29: ffff8000148f37d0 x28: ffff000109e54000 x27: ffff000109e54000
x26: ffff0001046e6000 x25: ffff000107f24f80 x24: ffff80000eeb3bf0
x23: 0000000000000000 x22: 0000000000000000 x21: 0000000000000000
x20: 0000000000000000 x19: 0000000000000016 x18: ffff000107f24f80
x17: 0000000000000050 x16: 0000000000000000 x15: 0000000000000000
x14: 0000000000000002 x13: 0000000000000005 x12: 0000000000040000
x11: 000000000003ffff x10: ffff80001d524000 x9 : 0000000000000001
x8 : ffff80000d8f7000 x7 : ffff800008188fe8 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000016 x0 : 0000000000040d40
Call trace:
 __alloc_pages+0x150/0x1fc mm/page_alloc.c:5491
 alloc_pages+0x374/0x484
 kmalloc_order+0x34/0x104 mm/slab_common.c:930
 kmalloc_order_trace+0x2c/0x7c mm/slab_common.c:946
 kmalloc_large include/linux/slab.h:529 [inline]
 __kmalloc+0x2ec/0x394 mm/slub.c:4413
 kmalloc_array include/linux/slab.h:640 [inline]
 kcalloc include/linux/slab.h:671 [inline]
 compute_bitstructs fs/gfs2/rgrp.c:766 [inline]
 read_rindex_entry fs/gfs2/rgrp.c:931 [inline]
 gfs2_ri_update+0x1a4/0x7e4 fs/gfs2/rgrp.c:1001
 gfs2_rindex_update+0x1b0/0x21c fs/gfs2/rgrp.c:1051
 init_inodes+0x11c/0x184 fs/gfs2/ops_fstype.c:910
 gfs2_fill_super+0x630/0x874 fs/gfs2/ops_fstype.c:1240
 get_tree_bdev+0x1e8/0x2a0 fs/super.c:1323
 gfs2_get_tree+0x30/0xc0 fs/gfs2/ops_fstype.c:1323
 vfs_get_tree+0x40/0x140 fs/super.c:1530
 do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040
 path_mount+0x358/0x914 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __arm64_sys_mount+0x2f8/0x408 fs/namespace.c:3568
 __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:624
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:642
 el0t_64_sync+0x18c/0x190
irq event stamp: 46508
hardirqs last  enabled at (46507): [<ffff80000bfd8fbc>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last  enabled at (46507): [<ffff80000bfd8fbc>] _raw_spin_unlock_irqrestore+0x48/0x8c kernel/locking/spinlock.c:194
hardirqs last disabled at (46508): [<ffff80000bfc6674>] el1_dbg+0x24/0x5c arch/arm64/kernel/entry-common.c:395
softirqs last  enabled at (46504): [<ffff800009272c30>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (46502): [<ffff800009272bfc>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ 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.

             reply	other threads:[~2022-09-16  6:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16  6:06 syzbot [this message]
2022-10-22 11:11 ` [Cluster-devel] [syzbot] WARNING in gfs2_ri_update syzbot
2022-10-22 11:11   ` syzbot
2022-10-25  9:54   ` [Cluster-devel] " Andrew Price
2022-10-25  9:54     ` Andrew Price

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=000000000000075fb105e8c52ada@google.com \
    --to=syzbot+f8bc4176e51e87e0928f@syzkaller.appspotmail.com \
    --cc=agruenba@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpeterso@redhat.com \
    --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.