From: Michal Hocko <mhocko@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Mike Manning <mmanning@vyatta.att-mail.com>,
stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mel Gorman <mgorman@techsingularity.net>,
linux-mm <linux-mm@kvack.org>
Subject: Re: stable request: mm, page_alloc: actually ignore mempolicies for high priority allocations
Date: Thu, 8 Nov 2018 10:11:39 +0100 [thread overview]
Message-ID: <20181108091139.GR27423@dhcp22.suse.cz> (raw)
In-Reply-To: <4ad07955-05d5-80ea-ebf1-876b0dc6347a@suse.cz>
On Thu 08-11-18 10:06:35, Vlastimil Babka wrote:
> On 11/8/18 10:01 AM, Michal Hocko wrote:
> > On Thu 08-11-18 08:30:40, Mike Manning wrote:
> > [...]
> >> 1) The original commit was not suitable for backport to 4.14 and should
> >> be reverted.
> >
> > Yes, the original patch hasn't been marked for the stable tree and as
> > such shouldn't have been backported. Even though it looks simple enough
> > it is not really trivial.
>
> I think you confused the two patches.
>
> Original commit 1d26c112959f ("mm, page_alloc: do not break
> __GFP_THISNODE by zonelist reset") was marked for stable, especially
> pre-4.7 where SLAB could be potentially broken.
You are right. My apology!
> Commit d6a24df00638 ("mm, page_alloc: actually ignore mempolicies for
> high priority allocations") was not marked stable and is being requested
> in this thread. But I'm reluctant to agree with this without properly
> understanding what went wrong.
Agreed
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-11-08 9:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a66fb268-74fe-6f4e-a99f-3257b8a5ac3b@vyatta.att-mail.com>
2018-11-08 7:54 ` Vlastimil Babka
2018-11-08 8:30 ` Mike Manning
2018-11-08 9:01 ` Michal Hocko
2018-11-08 9:06 ` Vlastimil Babka
2018-11-08 9:11 ` Michal Hocko [this message]
2018-11-08 9:41 ` Mike Manning
2018-12-28 10:49 ` Greg Kroah-Hartman
2018-11-08 9:32 ` Vlastimil Babka
2018-11-08 10:01 ` Mike Manning
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=20181108091139.GR27423@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mmanning@vyatta.att-mail.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
/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