From: Christoph Hellwig <hch@infradead.org>
To: syzbot <syzbot+359a67b608de1ef72f65@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, apopple@nvidia.com, baohua@kernel.org,
byungchul@sk.com, cem@kernel.org, david@fromorbit.com,
david@redhat.com, gourry@gourry.net, harry.yoo@oracle.com,
joshua.hahnjy@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-xfs@vger.kernel.org,
matthew.brost@intel.com, mhocko@suse.com,
penguin-kernel@i-love.sakura.ne.jp, rakie.kim@sk.com,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz,
willy@infradead.org, ying.huang@linux.alibaba.com,
ziy@nvidia.com
Subject: Re: [syzbot] [mm?] WARNING in xfs_init_fs_context
Date: Sun, 28 Sep 2025 23:40:33 -0700 [thread overview]
Message-ID: <aNop4ZBrfuqrX40Y@infradead.org> (raw)
In-Reply-To: <68d973fc.a00a0220.102ee.002b.GAE@google.com>
This looks like slub turning a < PAGE_SIZE allocation into a order > 0
folio allocation, which the page allocator then complains about.
We'll either need to make slab not propagate < PAGE_SIZE allocations
to order > 0 page allocation, or make the page allocator handle the
latter.
And XFS shouldn't need the NOFAIL allocation here, but this will break
things elsewhere as well.
next prev parent reply other threads:[~2025-09-29 6:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 22:47 syzbot
2025-07-01 15:01 ` Zi Yan
[not found] ` <1921ec99-7abb-42f1-a56b-d1f0f5bc1377@I-love.SAKURA.ne.jp>
2025-07-02 7:30 ` Vlastimil Babka
2025-07-04 8:26 ` Harry Yoo
2025-07-07 16:57 ` Vlastimil Babka
2025-07-07 22:10 ` Dave Chinner
2025-07-08 8:50 ` Vlastimil Babka
2025-09-28 17:44 ` syzbot
2025-09-29 6:40 ` Christoph Hellwig [this message]
2025-09-29 7:05 ` Vlastimil Babka
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=aNop4ZBrfuqrX40Y@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=baohua@kernel.org \
--cc=byungchul@sk.com \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--cc=david@redhat.com \
--cc=gourry@gourry.net \
--cc=harry.yoo@oracle.com \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=mhocko@suse.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rakie.kim@sk.com \
--cc=syzbot+359a67b608de1ef72f65@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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