linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Amit Pundir <amit.pundir@linaro.org>
To: Minchan Kim <minchan@kernel.org>, linux-mm@kvack.org
Cc: Vlastimil Babka <vbabka@suse.cz>,
	Mel Gorman <mgorman@techsingularity.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [for-4.9.y] Patch series "use up highorder free pages before OOM"
Date: Mon, 7 Jan 2019 16:37:37 +0530	[thread overview]
Message-ID: <CAMi1Hd0fZwp7WzGhLSmWG3K+DS+nwT9P9o=zAOGRFDDhjpnGpQ@mail.gmail.com> (raw)

Hi Minchan,

Kindly review your following mm/OOM upstream fixes for stable 4.9.y.

88ed365ea227 ("mm: don't steal highatomic pageblock")
04c8716f7b00 ("mm: try to exhaust highatomic reserve before the OOM")
29fac03bef72 ("mm: make unreserve highatomic functions reliable")

One of the patch from this series:
4855e4a7f29d ("mm: prevent double decrease of nr_reserved_highatomic")
has already been picked up for 4.9.y.

The original patch series https://lkml.org/lkml/2016/10/12/77 was sort
of NACked for stable https://lkml.org/lkml/2016/10/12/655 because no
one else reported this OOM behavior on lkml. And the only reason I'm
bringing this up again, for stable-4.9.y tree, is that msm-4.9 Android
trees cherry-picked this whole series as is for their production devices.

Are there any concerns around this series, in case I submit it to
stable mailing list for v4.9.y?

Regards,
Amit Pundir

             reply	other threads:[~2019-01-07 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 11:07 Amit Pundir [this message]
2019-01-07 11:07 ` Amit Pundir
2019-01-07 11:47 ` Minchan Kim
2019-01-07 14:38   ` Amit Pundir
2019-01-07 14:38     ` Amit Pundir

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='CAMi1Hd0fZwp7WzGhLSmWG3K+DS+nwT9P9o=zAOGRFDDhjpnGpQ@mail.gmail.com' \
    --to=amit.pundir@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=minchan@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