stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Build error in 3.18.y-stable-queue (s390)
Date: Sun, 27 Mar 2016 01:41:14 -0400	[thread overview]
Message-ID: <56F7727A.5020806@oracle.com> (raw)
In-Reply-To: <20160324180155.GA15991@roeck-us.net>

On 03/24/2016 02:01 PM, Guenter Roeck wrote:
> On Thu, Mar 24, 2016 at 08:38:27AM -0400, Sasha Levin wrote:
>> Thanks for the report Guenter!
>>
>> On 03/23/2016 12:21 AM, Guenter Roeck wrote:
>>> 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.
>>
>> Should be fixed, I backported "mm: account pmd page tables to the process" as well.
>>
>>>> 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.
>>
>> I've grabbed that commit.
>>
> 
> Now I get:
> 
> alpha, m32r, m68k, microblaze, parisc, sparc:
> 
> mm/mmap.c: In function 'exit_mmap':
> mm/mmap.c:2786:2: error: 'PUD_SHIFT' undeclared
> 
> s390:
> 
> ./arch/s390/include/asm/mmu_context.h: In function 'init_new_context':
> ./arch/s390/include/asm/mmu_context.h:30:22: error:
> 	'_ASCE_TYPE_REGION3' undeclared

Should be fixed now, I hope.

I better get more than just x86/ARM for cross compiling :/


Thanks,
Sasha


  reply	other threads:[~2016-03-27  5:41 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 [this message]
2016-03-27 15:35         ` Guenter Roeck
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=56F7727A.5020806@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=linux@roeck-us.net \
    --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).