From: Michal Hocko <mhocko@suse.com>
To: Alexey Makhalov <amakhalov@vmware.com>
Cc: Dennis Zhou <dennis@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"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: Mon, 15 Nov 2021 13:58:34 +0100 [thread overview]
Message-ID: <YZJZes9Gz9fe7bCC@dhcp22.suse.cz> (raw)
In-Reply-To: <B8B7E3FA-6EAB-46B7-95EB-5A31395C8ADE@vmware.com>
On Mon 15-11-21 11:04:16, Alexey Makhalov wrote:
> Hi Michal,
>
> >
> > I have asked several times for details about the specific setup that has
> > led to the reported crash. Without much success so far. Reproduction
> > steps would be the first step. That would allow somebody to work on this
> > at least if Alexey doesn't have time to dive into this deeper.
> >
>
> I didn’t know that repro steps are still not clear.
>
> To reproduce the panic you need to have a system, where you can hot add
> the CPU that belongs to memoryless NUMA node which is not present and onlined
> yet. In other words, by hot adding CPU, you will add both CPU and NUMA node
> at the same time.
There seems to be something different in your setup because memory less
nodes have reportedly worked on x86. I suspect something must be
different in your setup. Maybe it is that you are adding a cpu that is
outside of possible cpus intialized during boot time. Those should have
their nodes initialized properly - at least per init_cpu_to_node. Your
report doesn't really explain how the cpu is hotadded. Maybe you are
trying to do something that has never been supported on x86.
It would be really great if you can provide more information in the
original email thread. E.g. boot time messges and then more details
about the hotplug operation as well (e.g. which cpu, the node
association, how it is injected to the guest etc.).
Thanks!
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-11-15 12:59 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 ` 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 [this message]
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
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=YZJZes9Gz9fe7bCC@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=amakhalov@vmware.com \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®