All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Miles Chen <miles.chen@mediatek.com>
Cc: stable@vger.kernel.org
Subject: Re: backport commit ("739f79fc9db1 mm: memcontrol: fix NULL pointer crash in test_clear_page_writeback()") to linux-4.9-stable
Date: Tue, 11 Jun 2019 13:18:17 +0200	[thread overview]
Message-ID: <20190611111817.GA12260@kroah.com> (raw)
In-Reply-To: <20190611103407.GA3486@kroah.com>

On Tue, Jun 11, 2019 at 12:34:07PM +0200, Greg KH wrote:
> On Tue, Jun 11, 2019 at 04:57:47PM +0800, Miles Chen wrote:
> > Hi reviewers,
> > 
> > I suggest to backport commit "739f79fc9db1 mm: memcontrol: fix NULL
> > pointer crash in test_clear_page_writeback()" to linux-4.9 stable tree.
> > 
> > This email reports a NULL pointer crash in test_clear_page_writeback()
> > in android common kernel-4.9. There is a fix ("739f79fc9db1 mm:
> > memcontrol: fix NULL pointer crash in test_clear_page_writeback()") in
> > kernel-4.13.
> > 
> > 
> > commit: 739f79fc9db1b38f96b5a5109b247a650fbebf6d
> > subject: mm: memcontrol: fix NULL pointer crash in
> > test_clear_page_writeback()
> > kernel version to apply to: Linux-4.9
> 
> It does not apply cleanly to the 4.9.y tree, can you provide a working
> backport of it that I can apply?

Also be sure to cc: all of the people involved in that patch (the author
and the cc and signed-off-by list) so they can weigh in if they do not
feel that this patch should be backported to the older kernel.

thanks,

greg k-h

  reply	other threads:[~2019-06-11 11:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11  8:57 backport commit ("739f79fc9db1 mm: memcontrol: fix NULL pointer crash in test_clear_page_writeback()") to linux-4.9-stable Miles Chen
2019-06-11 10:34 ` Greg KH
2019-06-11 11:18   ` Greg KH [this message]
2019-06-11 11:39     ` Miles Chen
2019-06-11 11:57       ` Greg KH

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=20190611111817.GA12260@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=miles.chen@mediatek.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 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.