mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: CJ <firefly0158@163.com>
To: shaggy@kernel.org
Cc: jfs-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	syzbot+50ede9e39602b45e19f9@syzkaller.appspotmail.com
Subject: [BUG] jfs: kernel BUG in dbFindBits on v7.2-rc3
Date: Thu, 3 Sep 2026 15:01:24 +0800 (CST)	[thread overview]
Message-ID: <714a38e2.5550.1a06612825a.Coremail.firefly0158@163.com> (raw)


Hi,


I am reporting that kernel BUG in dbFindBits remains reproducible with a
migrated syzkaller reproducer on Linux 7.2-rc3. The tested HEAD commit is
a13c140cc289c0b7b3770bce5b3ad42ab35074aa.


The reproducer mounts a crafted JFS image and creates a file, causing block
allocation through dbAlloc(), dbAllocAG(), and dbAllocDmapLev().


The allocator reaches dbFindBits() with inconsistent dmap metadata and
triggers a kernel BUG followed by a fatal exception.


This looks like missing validation of corrupted JFS dmap state before the
allocation search reaches an internal invariant in dbFindBits().


This issue was previously reported at:


https://syzkaller.appspot.com/bug?extid=50ede9e39602b45e19f9


Reproducer:


syz reproducer: https://pastebin.com/raw/SPiRnuQU


console output: https://pastebin.com/raw/kiTmEiws
kernel config: https://pastebin.com/raw/S0X5SqR7


Kernel:


HEAD commit: a13c140cc289c0b7b3770bce5b3ad42ab35074aa
git tree: torvalds/linux
kernel version: 7.2.0-rc3 #1 PREEMPT(full)
tested tag: v7.2-rc3


Let me know if you need more details or testing.


Best regards

                 reply	other threads:[~2026-09-03  7:02 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=714a38e2.5550.1a06612825a.Coremail.firefly0158@163.com \
    --to=firefly0158@163.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@kernel.org \
    --cc=syzbot+50ede9e39602b45e19f9@syzkaller.appspotmail.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®