From: Wei Yang <richard.weiyang@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Michal Hocko <mhocko@suse.com>,
Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, dave.hansen@intel.com,
linux-mm@kvack.org
Subject: Re: [PATCH] mm, page_alloc: fix calculation of pgdat->nr_zones
Date: Tue, 4 Dec 2018 09:11:14 +0000 [thread overview]
Message-ID: <20181204091114.cqzepljxxrulju4v@master> (raw)
In-Reply-To: <20181204090500.GR235790@sasha-vm>
On Tue, Dec 04, 2018 at 04:05:04AM -0500, Sasha Levin wrote:
>On Mon, Nov 19, 2018 at 02:38:51PM +0100, Michal Hocko wrote:
>> Forgot to mention that this should probably go to stable. Having an
>> incorrect nr_zones might result in all sorts of problems which would be
>> quite hard to debug (e.g. reclaim not considering the movable zone).
>> I do not expect many users would suffer from this it but still this is
>> trivial and obviously right thing to do so backporting to the stable
>> tree shouldn't be harmful (last famous words).
>>
>> Cc: stable # since 4.13
>>
>> older tress would have to be checked explicitly.
>
>While the final commit included Michal's response, it didn't have a
>stable tag. Could someone confirm it should go in stable?
>
I think Michal wants it into stable.
>--
>Thanks,
>Sasha
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2018-12-04 9:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 2:20 Wei Yang
2018-11-19 6:38 ` Anshuman Khandual
2018-11-20 3:22 ` Wei Yang
2018-11-19 9:48 ` Michal Hocko
2018-11-19 13:38 ` Michal Hocko
2018-12-04 9:05 ` Sasha Levin
2018-12-04 9:11 ` Wei Yang [this message]
2018-11-19 10:07 ` osalvador
2018-11-19 10:20 ` Michal Hocko
2018-11-19 14:15 ` Wei Yang
2018-11-19 14:23 ` Michal Hocko
2018-11-19 21:44 ` Wei Yang
2018-11-19 21:47 ` 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=20181204091114.cqzepljxxrulju4v@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=sashal@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