From: Guenter Roeck <linux@roeck-us.net>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Build error in 3.18.y-stable-queue (s390)
Date: Sun, 27 Mar 2016 08:35:23 -0700 [thread overview]
Message-ID: <56F7FDBB.2000209@roeck-us.net> (raw)
In-Reply-To: <56F7727A.5020806@oracle.com>
Hi Sasha,
On 03/26/2016 10:41 PM, Sasha Levin wrote:
...
>
> Should be fixed now, I hope.
>
Builds now all pass, but now I get runtime errors on arm and microblaze qemu tests.
WARNING: CPU: 0 PID: 33 at mm/mmap.c:2787 exit_mmap+0x1ac/0x230()
You'll need to also pick up commit b30fe6c7ced7 ("mm: fix false-positive warning
on exit due mm_nr_pmds(mm)") to fix that.
The s390 qemu test now builds, but the test itself gets a RCU stall and hangs.
Reverting "s390/mm: four page table levels vs. fork" fixes the problem.
Guenter
next prev parent reply other threads:[~2016-03-27 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 3:42 Build error in 3.18.y-stable-queue (s390) Guenter Roeck
2016-03-23 4:21 ` Guenter Roeck
2016-03-24 12:38 ` Sasha Levin
2016-03-24 18:01 ` Guenter Roeck
2016-03-27 5:41 ` Sasha Levin
2016-03-27 15:35 ` Guenter Roeck [this message]
2016-03-28 17:07 ` Sasha Levin
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=56F7FDBB.2000209@roeck-us.net \
--to=linux@roeck-us.net \
--cc=sasha.levin@oracle.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 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).