All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Manning <mmanning@vyatta.att-mail.com>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Vlastimil Babka <vbabka@suse.cz>
Subject: stable request: mm, page_alloc: actually ignore mempolicies for high priority allocations
Date: Wed, 7 Nov 2018 17:33:43 +0000	[thread overview]
Message-ID: <a66fb268-74fe-6f4e-a99f-3257b8a5ac3b@vyatta.att-mail.com> (raw)

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> ("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. The reason this is
happening is not clear, with this commit only found by bisect.
Fortunately the requested commit resolves the issue.

Best Regards,

Mike Manning

             reply	other threads:[~2018-11-08  6:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 17:33 Mike Manning [this message]
2018-11-08  7:54 ` stable request: mm, page_alloc: actually ignore mempolicies for high priority allocations Vlastimil Babka
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
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=a66fb268-74fe-6f4e-a99f-3257b8a5ac3b@vyatta.att-mail.com \
    --to=mmanning@vyatta.att-mail.com \
    --cc=gregkh@linuxfoundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.