From: Michal Hocko <mhocko@kernel.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: lukasz.odzioba@intel.com, linux-kernel@vger.kernel.org,
xen-devel@lists.xensource.com, boris.ostrovsky@oracle.com,
david.vrabel@citrix.com, stable@vger.kernel.org,
akpm@linux-foundation.org, Sasha Levin <sasha.levin@oracle.com>
Subject: Re: Is: 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: Tue, 19 Jul 2016 10:32:17 +0200 [thread overview]
Message-ID: <20160719083216.GA9490@dhcp22.suse.cz> (raw)
In-Reply-To: <20160718153046.GA26126@char.us.oracle.com>
[CCing Sasha]
On Mon 18-07-16 11:30:46, Konrad Rzeszutek Wilk wrote:
> Hey Lukasz,
>
> We found that your patch in the automated Xen test-case ends up
> OOMing the box when trying to install guests. This worked prior
> to your patch.
>
> See serial log:
> http://logs.test-lab.xenproject.org/osstest/logs/97597/test-amd64-i386-qemut-rhel6hvm-amd/serial-pinot0.log
>
> Would it be OK to revert this patch from the stable trees?
The fix up is trivial so I believe it would be better to apply the
follow up fix
http://lkml.kernel.org/r/20160714175521.3675e3d6@gandalf.local.home
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2016-07-19 8:32 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
2016-07-21 14:23 ` Michal Hocko
2016-07-21 17:24 ` Sebastian Gottschall
2016-07-19 8:32 ` Michal Hocko [this message]
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=20160719083216.GA9490@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--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=sasha.levin@oracle.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).