From: Michal Hocko <mhocko@kernel.org>
To: Zaslonko Mikhail <zaslonko@linux.vnet.ibm.com>
Cc: Mikhail Zaslonko <zaslonko@linux.ibm.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Pavel.Tatashin@microsoft.com,
osalvador@suse.de, gerald.schaefer@de.ibm.com
Subject: Re: [PATCH] memory_hotplug: fix the panic when memory end is not on the section boundary
Date: Wed, 12 Sep 2018 14:21:32 +0200 [thread overview]
Message-ID: <20180912122132.GF10951@dhcp22.suse.cz> (raw)
In-Reply-To: <04b427ad-df4e-67bd-2942-2a7a2cccf1aa@linux.vnet.ibm.com>
On Tue 11-09-18 16:06:23, Zaslonko Mikhail wrote:
[...]
> > Well, I am afraid this is not the proper solution. We are relying on the
> > full pageblock worth of initialized struct pages at many other place. We
> > used to do that in the past because we have initialized the full
> > section but this has been changed recently. Pavel, do you have any ideas
> > how to deal with this partial mem sections now?
>
> I think this is not related to the recent changes of memory initialization.
> If
> you mean deferred init case, the problem exists even without
> CONFIG_DEFERRED_STRUCT_PAGE_INIT kernel option.
This is more about struct page initialization (which doesn't clear
whole) memmap area and as such it stays unitialized. So you are right
this is a much older issue we just happened to not notice without
explicit memmap poisoning.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-09-12 12:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 12:35 [PATCH] memory_hotplug: fix the panic when memory end is not on the section boundary Mikhail Zaslonko
2018-09-10 13:17 ` Michal Hocko
2018-09-10 13:46 ` Pasha Tatashin
2018-09-10 13:59 ` Michal Hocko
2018-09-10 14:11 ` Pasha Tatashin
2018-09-10 14:19 ` Michal Hocko
2018-09-10 14:32 ` Pasha Tatashin
2018-09-10 14:41 ` Michal Hocko
2018-09-10 15:26 ` Pasha Tatashin
2018-09-11 9:16 ` Michal Hocko
2018-09-12 14:28 ` Gerald Schaefer
2018-09-11 14:08 ` Zaslonko Mikhail
2018-09-11 14:06 ` Zaslonko Mikhail
2018-09-12 12:21 ` Michal Hocko [this message]
2018-09-12 13:03 ` Gerald Schaefer
2018-09-12 13:39 ` Michal Hocko
2018-09-12 14:27 ` Gerald Schaefer
2018-09-12 14:40 ` Pasha Tatashin
2018-09-12 15:51 ` Gerald Schaefer
2018-10-24 19:28 ` Zaslonko Mikhail
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=20180912122132.GF10951@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=Pavel.Tatashin@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=gerald.schaefer@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=zaslonko@linux.ibm.com \
--cc=zaslonko@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).