xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	"Odzioba, Lukasz" <lukasz.odzioba@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
	"david.vrabel@citrix.com" <david.vrabel@citrix.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	Sebastian Gottschall <s.gottschall@dd-wrt.com>
Subject: Re: Revert c5ad33184354260be6d05de57e46a5498692f6d6 "mm/swap.c: flush lru pvecs on compound page arrival" from stable tree? Was:[osstest-admin@xenproject.org: [Xen-devel] [linux-4.1 bisection] complete test-amd64-i386-qemut-rhel6hvm-amd]
Date: Thu, 21 Jul 2016 13:45:40 +0100	[thread overview]
Message-ID: <22416.50164.521430.604730@mariner.uk.xensource.com> (raw)
In-Reply-To: <73189037-1a4e-915a-7120-112f2afe3342@dd-wrt.com>

I see that linux-4.1.y is still at 5880876e9469 which has the serious
bug introduced by the backport c5ad33184354 "mm/swap.c: flush lru
pvecs on compound page arrival".

The analogous problem is also still affecting at least linux-3.18.y.

Is there some problem with reverting this patch in the stable
branches ?

Thanks,
Ian.

  reply	other threads:[~2016-07-21 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18 15:30 Is: Revert c5ad33184354260be6d05de57e46a5498692f6d6 "mm/swap.c: flush lru pvecs on compound page arrival" from stable tree? Was:[osstest-admin@xenproject.org: [linux-4.1 bisection] complete test-amd64-i386-qemut-rhel6hvm-amd] Konrad Rzeszutek Wilk
2016-07-18 15:48 ` Revert c5ad33184354260be6d05de57e46a5498692f6d6 "mm/swap.c: flush lru pvecs on compound page arrival" from stable tree? Was:[osstest-admin@xenproject.org: [Xen-devel] " Odzioba, Lukasz
2016-07-18 16:18   ` Revert c5ad33184354260be6d05de57e46a5498692f6d6 "mm/swap.c: flush lru pvecs on compound page arrival" from stable tree? Was:[osstest-admin@xenproject.org: " Konrad Rzeszutek Wilk
2016-07-18 16:53     ` Revert c5ad33184354260be6d05de57e46a5498692f6d6 "mm/swap.c: flush lru pvecs on compound page arrival" from stable tree? Was:[osstest-admin@xenproject.org: [Xen-devel] " Sebastian Gottschall
2016-07-21 12:45       ` Ian Jackson [this message]
2016-07-21 14:23         ` Michal Hocko
2016-07-21 17:24           ` Sebastian Gottschall
2016-07-19  8:32 ` Is: " Michal Hocko
2016-07-19  8:35   ` Is: Revert c5ad33184354260be6d05de57e46a5498692f6d6 "mm/swap.c: flush lru pvecs on compound page arrival" from stable tree? Was:[osstest-admin@xenproject.org: " Sebastian Gottschall
2016-07-19  9:23     ` Is: Revert c5ad33184354260be6d05de57e46a5498692f6d6 "mm/swap.c: flush lru pvecs on compound page arrival" from stable tree? Was:[osstest-admin@xenproject.org: [Xen-devel] " Michal Hocko

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=22416.50164.521430.604730@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=akpm@linux-foundation.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz.odzioba@intel.com \
    --cc=s.gottschall@dd-wrt.com \
    --cc=stable@vger.kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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;
as well as URLs for NNTP newsgroup(s).