From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Hocko <mhocko@suse.com>
Cc: Dennis Zhou <dennis@kernel.org>,
Alexey Makhalov <amakhalov@vmware.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"cl@linux.com" <cl@linux.com>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
"osalvador@suse.de" <osalvador@suse.de>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"tj@kernel.org" <tj@kernel.org>
Subject: Re: + mm-fix-panic-in-__alloc_pages.patch added to -mm tree
Date: Tue, 14 Dec 2021 12:57:48 -0800 [thread overview]
Message-ID: <20211214125748.974a400f0b05a633f9b971b7@linux-foundation.org> (raw)
In-Reply-To: <Ybht6kqwI0aPx3Jr@dhcp22.suse.cz>
On Tue, 14 Dec 2021 11:11:54 +0100 Michal Hocko <mhocko@suse.com> wrote:
> > I need some clarification here. It sounds like memoryless nodes work on
> > x86, but hotplug + memoryless nodes isn't a supported use case or you're
> > introducing it as a new use case?
> >
> > If this is a new use case, then I'm inclined to say this patch should
> > NOT go in and a proper fix should be implemented on hotplug's side. I
> > don't want to be in the business of having/seeing this conversation
> > reoccur because we just papered over this issue in percpu.
>
> The patch still seems to be in the mmotm tree. I have sent a different
> fix candidate [1] which should be more robust and cover also other potential
> places.
>
> [1] http://lkml.kernel.org/r/20211214100732.26335-1-mhocko@kernel.org
Is cool, I'm paying attention.
We do want something short and simple for backporting to -stable (like
Alexey's patch) so please bear that in mind while preparing an
alternative.
next prev parent reply other threads:[~2021-12-14 20:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211108205031.UxDPHBZWa%akpm@linux-foundation.org>
2021-11-09 8:37 ` + mm-fix-panic-in-__alloc_pages.patch added to -mm tree Michal Hocko
2021-11-09 8:42 ` David Hildenbrand
2021-11-09 11:00 ` Michal Hocko
2021-11-12 18:20 ` Dennis Zhou
2021-11-15 10:41 ` Michal Hocko
2021-11-15 11:04 ` Alexey Makhalov
2021-11-15 12:58 ` Michal Hocko
2021-11-15 23:11 ` Alexey Makhalov
2021-11-16 3:52 ` Dennis Zhou
2021-11-16 12:30 ` Christoph Lameter
2021-11-16 15:41 ` Michal Hocko
2021-12-14 10:11 ` Michal Hocko
2021-12-14 20:57 ` Andrew Morton [this message]
2021-12-15 10:05 ` Michal Hocko
2021-12-15 12:20 ` Michal Hocko
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=20211214125748.974a400f0b05a633f9b971b7@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=amakhalov@vmware.com \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.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).