mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: CJ <firefly0158@163.com>
To: rpeterso@redhat.com, agruenba@redhat.com
Cc: cluster-devel@redhat.com, linux-kernel@vger.kernel.org,
	syzbot+5c0ca4a146e6115b14f7@syzkaller.appspotmail.com
Subject: [BUG] gfs2: allocation warning in gfs2_ri_update
Date: Thu, 3 Sep 2026 15:09:54 +0800 (CST)	[thread overview]
Message-ID: <73b862eb.57a1.1a0661a4d73.Coremail.firefly0158@163.com> (raw)


Hi,


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


The reproducer mounts a crafted GFS2 image and processes its resource-group
index during filesystem initialization.


Corrupted resource-index data causes gfs2_ri_update() to request an invalid
or excessive allocation, leading to a page allocator warning.


This looks like insufficient bounds validation of resource-index values
before they are converted into an allocation size.


This issue was previously reported at:


https://syzkaller.appspot.com/bug?extid=5c0ca4a146e6115b14f7


Reproducer:


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


console output: https://pastebin.com/raw/QjEkRSwz
kernel config: https://pastebin.com/raw/tu1S3js9


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:10 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=73b862eb.57a1.1a0661a4d73.Coremail.firefly0158@163.com \
    --to=firefly0158@163.com \
    --cc=agruenba@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpeterso@redhat.com \
    --cc=syzbot+5c0ca4a146e6115b14f7@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®