From: Vlastimil Babka <vbabka@suse.cz>
To: mmanning@vyatta.att-mail.com, stable@vger.kernel.org
Cc: 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 08:54:07 +0100 [thread overview]
Message-ID: <08ae2e51-672a-37de-2aa6-4e49dbc9de02@suse.cz> (raw)
In-Reply-To: <a66fb268-74fe-6f4e-a99f-3257b8a5ac3b@vyatta.att-mail.com>
+CC linux-mm
On 11/7/18 6:33 PM, Mike Manning wrote:
> Hello, Please consider backporting to 4.14.y the following commit from
> kernel-net-next by Vlastimil Babka [CC'ed]:
>
> d6a24df00638 ("mm, page_alloc: actually ignore mempolicies for high
> priority allocations") It cherry-picks cleanly and builds fine.
>
> The reason for the request is that the commit 1d26c112959f
> <http://stash.eng.vyatta.net:7990/projects/VC/repos/linux-vyatta/commits/1d26c112959f>A ("mm,
> page_alloc:do not break __GFP_THISNODE by zonelist reset") that was
> previously backported to 4.14.y broke some of our functionality after we
> upgraded from an earlier 4.14 kernel without the fix.
Well, that's very surprising! Could you be more specific about what
exactly got broken?
> The reason this is
> happening is not clear, with this commit only found by bisect.
> Fortunately the requested commit resolves the issue.
I would like to understand the problem first, because I currently can't
imagine how the first commit could break something and the second fix it.
> Best Regards,
>
> Mike Manning
>
next parent reply other threads:[~2018-11-08 7:54 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 [this message]
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
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=08ae2e51-672a-37de-2aa6-4e49dbc9de02@suse.cz \
--to=vbabka@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mmanning@vyatta.att-mail.com \
--cc=stable@vger.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