From: Andrew Morton <akpm@linux-foundation.org>
To: "Shi, Yang" <yang.shi@linaro.org>
Cc: iamjoonsoo.kim@lge.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] mm: move page_ext_init after all struct pages are initialized
Date: Thu, 19 May 2016 16:21:07 -0700 [thread overview]
Message-ID: <20160519162107.372d19eac129d590ea160203@linux-foundation.org> (raw)
In-Reply-To: <6dd46bac-a0e4-d3c0-ded3-cbacc7f4a4ff@linaro.org>
On Thu, 19 May 2016 15:35:15 -0700 "Shi, Yang" <yang.shi@linaro.org> wrote:
> On 5/19/2016 3:30 PM, Andrew Morton wrote:
> > On Thu, 19 May 2016 14:29:05 -0700 Yang Shi <yang.shi@linaro.org> wrote:
> >
> >> When DEFERRED_STRUCT_PAGE_INIT is enabled, just a subset of memmap at boot
> >> are initialized, then the rest are initialized in parallel by starting one-off
> >> "pgdatinitX" kernel thread for each node X.
> >>
> >> If page_ext_init is called before it, some pages will not have valid extension,
> >> so move page_ext_init() after it.
> >>
> >
> > <stdreply>When fixing a bug, please fully describe the end-user impact
> > of that bug</>
>
> The kernel ran into the below oops which is same with the oops reported
> in
> http://ozlabs.org/~akpm/mmots/broken-out/mm-page_is_guard-return-false-when-page_ext-arrays-are-not-allocated-yet.patch.
So this patch makes
mm-page_is_guard-return-false-when-page_ext-arrays-are-not-allocated-yet.patch
obsolete?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-05-19 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 21:29 Yang Shi
2016-05-19 22:30 ` Andrew Morton
2016-05-19 22:35 ` Shi, Yang
2016-05-19 23:21 ` Andrew Morton [this message]
2016-05-19 23:26 ` Shi, Yang
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=20160519162107.372d19eac129d590ea160203@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yang.shi@linaro.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