From: Michal Hocko <mhocko@kernel.org>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Lukasz Odzioba <lukasz.odzioba@intel.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
stable@vger.kernel.org, xen-devel@lists.xensource.com,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: Linux 3.18 and Linux 4.1 reproducible OOM crashes under Xen
Date: Mon, 18 Jul 2016 13:25:33 +0200 [thread overview]
Message-ID: <20160718112533.GF22671@dhcp22.suse.cz> (raw)
In-Reply-To: <22412.47846.201172.197052@mariner.uk.xensource.com>
On Mon 18-07-16 12:17:58, Ian Jackson wrote:
> The Xen Project CI system (`osstest') reports that the current tip of
> the Linux 3.18 and Linux 4.1 stable branches have serious problems
> booting Xen.
>
> Our automatic bisector has completed its work and fingered (in 3.18)
> a2d8c5147532 "mm/swap.c: flush lru pvecs on compound page arrival"
> (and a backport of what seems to be the same commit to Linux 4.1).
Yes, this patch has been misbackported to the stable tree (at least 4.1
and maybe others which took it over from there). See
http://lkml.kernel.org/r/20160714175521.3675e3d6@gandalf.local.home
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2016-07-18 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 5:03 [linux-3.18 test] 97278: regressions - FAIL osstest service owner
2016-07-14 12:56 ` Linux 3.18 and Linux 4.1 reproducible OOM crashes Ian Jackson
2016-07-14 23:34 ` Konrad Rzeszutek Wilk
2016-07-15 10:00 ` Ian Jackson
2016-07-18 11:17 ` Linux 3.18 and Linux 4.1 reproducible OOM crashes under Xen Ian Jackson
2016-07-18 11:25 ` Michal Hocko [this message]
2016-07-18 11:43 ` Odzioba, Lukasz
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=20160718112533.GF22671@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ian.jackson@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=lukasz.odzioba@intel.com \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).