All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Yalin.Wang@sonymobile.com, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, stable@vger.kernel.org,
	Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Subject: Re: FAILED: patch "[PATCH] mm: add VM_BUG_ON_PAGE() to page_mapcount()" failed to apply to 4.4-stable tree
Date: Mon, 1 Jun 2020 16:15:22 +0200	[thread overview]
Message-ID: <20200601141522.GA722623@kroah.com> (raw)
In-Reply-To: <20200601140519.rm5lthhe6cf45567@black.fi.intel.com>

On Mon, Jun 01, 2020 at 05:05:19PM +0300, Kirill A. Shutemov wrote:
> On Mon, Jun 01, 2020 at 01:07:24PM +0200, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 4.4-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> 
> Please don't.
> 
> The patch known to cause trouble and going to be effectively reverted:
> 
> https://lore.kernel.org/r/159032779896.957378.7852761411265662220.stgit@buzz

Oops, I ment to say that 6988f31d558a ("mm: remove VM_BUG_ON(PageSlab())
from page_mapcount()") did not apply to the 4.4 tree and needs a working
backport.

I put in the wrong id as that is the commit that 6988f31d558a fixes.

So, if you could provide a working backport, that would be wonderful.

thanks,

greg k-h

  reply	other threads:[~2020-06-01 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 11:07 FAILED: patch "[PATCH] mm: add VM_BUG_ON_PAGE() to page_mapcount()" failed to apply to 4.4-stable tree gregkh
2020-06-01 14:05 ` Kirill A. Shutemov
2020-06-01 14:15   ` Greg KH [this message]
2020-06-01 14:30     ` Kirill A. Shutemov
2020-06-01 14:41       ` 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=20200601141522.GA722623@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Yalin.Wang@sonymobile.com \
    --cc=akpm@linux-foundation.org \
    --cc=khlebnikov@yandex-team.ru \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.