From: Peter Geis <pgwipeout@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Tejun Heo <tj@kernel.org>, Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org
Subject: Re: [BUG] page allocation failure reading procfs ipv6 configuration files with cgroups
Date: Mon, 22 Feb 2021 18:40:15 -0500 [thread overview]
Message-ID: <CAMdYzYojq--qWhxmpj4VL_feNjMFZcjN6q7mQL-+SWujScNzkQ@mail.gmail.com> (raw)
In-Reply-To: <20210220173605.GD2858050@casper.infradead.org>
On Sat, Feb 20, 2021 at 12:36 PM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Sat, Feb 20, 2021 at 12:29:18PM -0500, Peter Geis wrote:
> > Good Afternoon,
> >
> > I have been tracking down a regular bug that triggers when running OpenWRT in a lxd container.
> > Every ten minutes I was greeted with the following splat in the kernel log:
> >
> > [2122311.383389] warn_alloc: 3 callbacks suppressed
> > [2122311.383403] cat: page allocation failure: order:5, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=lxc.payload.openwrt,mems_allowed=0
>
> You want this patch:
>
> https://lore.kernel.org/linux-fsdevel/6345270a2c1160b89dd5e6715461f388176899d1.1612972413.git.josef@toxicpanda.com/
I've tested this patch against 5.10.17 for 36 hours and can confirm it
solves the problem.
Thank you.
prev parent reply other threads:[~2021-02-22 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 17:29 [BUG] page allocation failure reading procfs ipv6 configuration files with cgroups Peter Geis
2021-02-20 17:36 ` Matthew Wilcox
2021-02-22 23:40 ` Peter Geis [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=CAMdYzYojq--qWhxmpj4VL_feNjMFZcjN6q7mQL-+SWujScNzkQ@mail.gmail.com \
--to=pgwipeout@gmail.com \
--cc=adobriyan@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=tj@kernel.org \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).