From: Harry Yoo <harry.yoo@oracle.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: chris.bainbridge@gmail.com, vbabka@suse.cz, surenb@google.com,
dsterba@suse.cz, hao.li@linux.dev, leitao@debian.org,
Liam.Howlett@oracle.com, zhao1.liu@intel.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-btrfs@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION] kswapd0: page allocation failure (bisected to "slab: add sheaves to most caches")
Date: Wed, 25 Feb 2026 11:10:10 +0900 [thread overview]
Message-ID: <aZ5aAlDDpUoZxx_g@hyeyoo> (raw)
In-Reply-To: <20260225015359.1495283-1-mikhail.v.gavrilov@gmail.com>
On Wed, Feb 25, 2026 at 06:53:59AM +0500, Mikhail Gavrilov wrote:
> I can confirm this issue on my system:
>
> Hardware: ASUS ROG STRIX B650E-I (AMD Ryzen), 64GB RAM
> Storage: btrfs with zram swap
> Kernel: 7.0.0-rc1 (commit 6de23f81a5e0+)
>
> I was seeing the same kswapd0 page allocation failures periodically
> under memory pressure with the identical call trace through
> alloc_from_pcs -> __pcs_replace_empty_main -> refill_objects ->
> allocate_slab.
>
> Chris's btrfs __GFP_NOWARN patch suppresses the btrfs-originated
> warnings, but after ~10 hours I hit the same sheaf refill failure
> from a different caller -- amdgpu via kmalloc:
>
> chrome: page allocation failure: order:0,
> mode:0xc0cc0(GFP_KERNEL|__GFP_COMP|__GFP_NOMEMALLOC)
>
> allocate_slab
> refill_objects
> __pcs_replace_empty_main
> __kmalloc_cache_noprof
> drm_suballoc_new
> amdgpu_sa_bo_new
Hi Mikhail,
In this case __GFP_NOWARN is not specified, so indeed
we need slab side fix.
> This confirms the fix needs to be on the slab side as Harry
> suggested -- adding __GFP_NOWARN to sheaf refill when there's
> a fallback path -- rather than patching individual callers.
Thanks for testing and sharing the result!
That's very helpful.
> Happy to test any slab-side fix.
Slab fix is submitted here, please feel free to test:
https://lore.kernel.org/linux-mm/20260223133322.16705-1-harry.yoo@oracle.com
--
Cheers,
Harry / Hyeonggon
prev parent reply other threads:[~2026-02-25 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 21:36 Chris Bainbridge
2026-02-23 8:41 ` Harry Yoo
2026-02-23 11:12 ` Chris Bainbridge
2026-02-23 11:59 ` Harry Yoo
2026-02-23 20:30 ` David Sterba
2026-02-25 1:53 ` Mikhail Gavrilov
2026-02-25 2:10 ` Harry Yoo [this message]
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=aZ5aAlDDpUoZxx_g@hyeyoo \
--to=harry.yoo@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=chris.bainbridge@gmail.com \
--cc=dsterba@suse.cz \
--cc=hao.li@linux.dev \
--cc=leitao@debian.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=zhao1.liu@intel.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