From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from bh-25.webhostbox.net ([208.91.199.152]:35217 "EHLO
	bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750717AbcCWEVF (ORCPT
	<rfc822;stable@vger.kernel.org>); Wed, 23 Mar 2016 00:21:05 -0400
Subject: Re: Build error in 3.18.y-stable-queue (s390)
To: stable <stable@vger.kernel.org>,
	Sasha Levin <sasha.levin@oracle.com>
References: <56F210BD.1060301@roeck-us.net>
From: Guenter Roeck <linux@roeck-us.net>
Message-ID: <56F219B0.3040107@roeck-us.net>
Date: Tue, 22 Mar 2016 21:21:04 -0700
MIME-Version: 1.0
In-Reply-To: <56F210BD.1060301@roeck-us.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On 03/22/2016 08:42 PM, Guenter Roeck wrote:
> Hi Sasha,
>
> s390 builds in v3.18.y-stable-queue fail as follows.
>
> ./arch/s390/include/asm/mmu_context.h: In function 'init_new_context':
> ./arch/s390/include/asm/mmu_context.h:33:3: error: implicit declaration of function 'mm_inc_nr_pmds'
>
> Culprit appears to be 's390/mm: four page table levels vs. fork'. It uses mm_inc_nr_pmds(),
> which does not exist in v3.18.
>
> I noticed that arm64:allmodconfig builds fail as well, but that is not a new problem and
> only seen with gcc 5.2 (or at least not with gcc 4.9.1). I'll see if I can track this down.
>

Fixing the arm64 problem will require patch f5e0a12ca2d9 ("arm64: psci: move psci firmware
calls out of line"). The patch doesn't apply cleanly; there is a minor conflict in the
arm64 Makefile. Let me know if you need me to send a backport.

Thanks,
Guenter