mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: CJ <firefly0158@163.com>
To: mark@fasheh.com, jlbec@evilplan.org, joseph.qi@linux.alibaba.com
Cc: ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: kernel BUG in ocfs2_reserve_suballoc_bits on v7.3-rc2
Date: Fri, 13 Nov 2026 11:47:22 +0800 (CST)	[thread overview]
Message-ID: <14bb82fe.33fe.1a1d30462b6.Coremail.firefly0158@163.com> (raw)


Hi,


I am reporting a kernel BUG in ocfs2_reserve_suballoc_bits. It is still reproducible on
Linux v7.3-rc2 (HEAD df2908090cda368b01ff43709f51890076c56157) with a syzkaller reproducer.
syzbot originally reported "kernel BUG in ocfs2_reserve_suballoc_bits" on linux-6.1
(https://syzkaller.appspot.com/bug?extid=487e39304129321dd253). The target console shows a matching failure signature.


The reproducer mounts a crafted OCFS2 image and creates a file, reaching the metadata suballocator while reserving blocks for the new inode.


On the target, the kernel reports:
  Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
  RIP: ocfs2_reserve_suballoc_bits


The diagnostic path is ocfs2_reserve_new_metadata_blocks -> ocfs2_calc_xattr_init -> ocfs2_mknod -> ocfs2_create.
It shares 5 key stack frames with the original kernel BUG
report, including ocfs2_reserve_new_metadata_blocks, ocfs2_mknod, ocfs2_create, path_openat.


This looks like the suballocator hitting an invariant failure while reserving metadata blocks for a new inode.


This is a follow-up for an existing syzbot report and describes an
observed failure, not a bisected root cause.


Reproducer:
  C reproducer: https://pastebin.com/raw/HwtDrmaz


console output: https://pastebin.com/raw/P3nKCetg
kernel config: https://syzkaller.appspot.com/text?tag=KernelConfig&x=b1adc0bfde2d8a4a


Kernel:
  HEAD commit: df2908090cda368b01ff43709f51890076c56157
  git tree: linux-stable
  kernel version: 7.3.0-rc2
  tested tag: v7.3-rc2


Let me know if you need more details or testing.


Thanks.


                 reply	other threads:[~2026-11-13  3:48 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=14bb82fe.33fe.1a1d30462b6.Coremail.firefly0158@163.com \
    --to=firefly0158@163.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@oss.oracle.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

all inboxes | Powered by JetHome®