All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Minchan Kim <minchan@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: [for-4.9.y] Patch series "use up highorder free pages before OOM", v3.
Date: Mon, 7 Jan 2019 10:48:52 +0100	[thread overview]
Message-ID: <20190107094852.GA31759@kroah.com> (raw)
In-Reply-To: <CAMi1Hd17jyBKgb53W_VbDfW2+jHRo405Hx5Z4FSuFeJEJT4vJg@mail.gmail.com>

On Mon, Jan 07, 2019 at 03:10:35PM +0530, Amit Pundir wrote:
> Hi Greg,
> 
> Kindly review and consider 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")
> 
> The original 4 patch series is archived here
> https://lkml.org/lkml/2016/10/12/77 for review.
> 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 and 4.4.y.
> 
> I ran into these fixes in one of the msm-4.9(android) trees.
> Cherry-picked and build tested on Linux 4.9.148 for
> ARCH=arm/arm64 defconfig.
> 
> Only the first patch from this series can be applied cleanly on
> v4.4.y, while others fail to apply cleanly due to OOM rework done in
> v4.7 release cycle, 0a0337e0d1d1 ("mm, oom: rework oom detection").
> Plus I don't see this series backported to v4.4 in any of the
> msm-4.4(android) trees either. So I'm skipping it for v4.4.y.

Can you get an ack from the mm developers that these really are viable
for backporting to older kernel trees as they solve a real issue?

thanks,

greg k-h

  reply	other threads:[~2019-01-07  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07  9:40 [for-4.9.y] Patch series "use up highorder free pages before OOM", v3 Amit Pundir
2019-01-07  9:48 ` Greg Kroah-Hartman [this message]
2019-01-07  9:55   ` Amit Pundir
2019-01-07 10:07     ` Greg Kroah-Hartman
2019-01-07 10:30       ` 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=20190107094852.GA31759@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=amit.pundir@linaro.org \
    --cc=minchan@kernel.org \
    --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 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.