From: Vlastimil Babka <vbabka@suse.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>, harry.yoo@oracle.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: Thu, 26 Feb 2026 17:31:01 +0100 [thread overview]
Message-ID: <64604c7e-5db9-49b9-b576-bbc627c8ddd1@suse.com> (raw)
In-Reply-To: <20260226162052.36121-1-mikhail.v.gavrilov@gmail.com>
On 2/26/26 17:20, Mikhail Gavrilov wrote:
> On Wed, Feb 25, 2026, Harry Yoo <harry.yoo@oracle.com> wrote:
>> Slab fix is submitted here, please feel free to test:
>>
>> https://lore.kernel.org/linux-mm/20260223133322.16705-1-harry.yoo@oracle.com
>
> No page allocation failures after 33 hours of uptime under normal
> desktop workload with memory pressure (64GB RAM, btrfs + zram swap,
> Chrome with many tabs, AMD GPU).
>
> Previously without this patch, I was seeing failures from both
> kswapd0/btrfs and chrome/amdgpu callers within 10 hours.
>
> Kernel: 7.0.0-rc1 (commit 7dff99b35460 + this patch)
> Hardware: ASUS ROG STRIX B650E-I, AMD Ryzen, 64GB RAM
>
> Tested-by: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Thanks, added to the commit.
prev parent reply other threads:[~2026-02-26 16:31 UTC|newest]
Thread overview: 9+ 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
2026-02-26 16:20 ` Mikhail Gavrilov
2026-02-26 16:31 ` Vlastimil Babka [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=64604c7e-5db9-49b9-b576-bbc627c8ddd1@suse.com \
--to=vbabka@suse.com \
--cc=Liam.Howlett@oracle.com \
--cc=chris.bainbridge@gmail.com \
--cc=dsterba@suse.cz \
--cc=hao.li@linux.dev \
--cc=harry.yoo@oracle.com \
--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