All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Howlett <liam.howlett@oracle.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the maple tree
Date: Thu, 17 Feb 2022 19:24:35 +0000	[thread overview]
Message-ID: <20220217192434.GA11800@willie-the-truck> (raw)
In-Reply-To: <20220217191857.6d9917c2@canb.auug.org.au>

On Thu, Feb 17, 2022 at 07:18:57PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the maple tree, today's linux-next build (arm64 defconfig)
> failed like this:
> 
> arch/arm64/kernel/elfcore.c: In function 'elf_core_extra_phdrs':
> arch/arm64/kernel/elfcore.c:13:35: error: 'struct mm_struct' has no member named 'mmap'
>    13 |                 for (vma = tsk->mm->mmap; vma; vma = vma->vm_next)      \
>       |                                   ^~
> arch/arm64/kernel/elfcore.c:69:9: note: in expansion of macro 'for_each_mte_vma'
>    69 |         for_each_mte_vma(current, vma)
>       |         ^~~~~~~~~~~~~~~~
> arch/arm64/kernel/elfcore.c:13:57: error: 'struct vm_area_struct' has no member named 'vm_next'
>    13 |                 for (vma = tsk->mm->mmap; vma; vma = vma->vm_next)      \
>       |                                                         ^~
> arch/arm64/kernel/elfcore.c:69:9: note: in expansion of macro 'for_each_mte_vma'
>    69 |         for_each_mte_vma(current, vma)
>       |         ^~~~~~~~~~~~~~~~
> arch/arm64/kernel/elfcore.c: In function 'elf_core_write_extra_phdrs':
> arch/arm64/kernel/elfcore.c:13:35: error: 'struct mm_struct' has no member named 'mmap'
>    13 |                 for (vma = tsk->mm->mmap; vma; vma = vma->vm_next)      \
>       |                                   ^~
> arch/arm64/kernel/elfcore.c:79:9: note: in expansion of macro 'for_each_mte_vma'
>    79 |         for_each_mte_vma(current, vma) {
>       |         ^~~~~~~~~~~~~~~~
> arch/arm64/kernel/elfcore.c:13:57: error: 'struct vm_area_struct' has no member named 'vm_next'
>    13 |                 for (vma = tsk->mm->mmap; vma; vma = vma->vm_next)      \
>       |                                                         ^~
> arch/arm64/kernel/elfcore.c:79:9: note: in expansion of macro 'for_each_mte_vma'
>    79 |         for_each_mte_vma(current, vma) {
>       |         ^~~~~~~~~~~~~~~~
> arch/arm64/kernel/elfcore.c: In function 'elf_core_extra_data_size':
> arch/arm64/kernel/elfcore.c:13:35: error: 'struct mm_struct' has no member named 'mmap'
>    13 |                 for (vma = tsk->mm->mmap; vma; vma = vma->vm_next)      \
>       |                                   ^~
> arch/arm64/kernel/elfcore.c:104:9: note: in expansion of macro 'for_each_mte_vma'
>   104 |         for_each_mte_vma(current, vma)
>       |         ^~~~~~~~~~~~~~~~
> arch/arm64/kernel/elfcore.c:13:57: error: 'struct vm_area_struct' has no member named 'vm_next'
>    13 |                 for (vma = tsk->mm->mmap; vma; vma = vma->vm_next)      \
>       |                                                         ^~
> arch/arm64/kernel/elfcore.c:104:9: note: in expansion of macro 'for_each_mte_vma'
>   104 |         for_each_mte_vma(current, vma)
>       |         ^~~~~~~~~~~~~~~~
> arch/arm64/kernel/elfcore.c: In function 'elf_core_write_extra_data':
> arch/arm64/kernel/elfcore.c:13:35: error: 'struct mm_struct' has no member named 'mmap'
>    13 |                 for (vma = tsk->mm->mmap; vma; vma = vma->vm_next)      \
>       |                                   ^~
> arch/arm64/kernel/elfcore.c:114:9: note: in expansion of macro 'for_each_mte_vma'
>   114 |         for_each_mte_vma(current, vma) {
>       |         ^~~~~~~~~~~~~~~~
> arch/arm64/kernel/elfcore.c:13:57: error: 'struct vm_area_struct' has no member named 'vm_next'
>    13 |                 for (vma = tsk->mm->mmap; vma; vma = vma->vm_next)      \
>       |                                                         ^~
> arch/arm64/kernel/elfcore.c:114:9: note: in expansion of macro 'for_each_mte_vma'
>   114 |         for_each_mte_vma(current, vma) {
>       |         ^~~~~~~~~~~~~~~~
> 
> Caused by commit
> 
>   b09e8361a4c3 ("mm: Remove the vma linked list")
> 
> interacting with commit
> 
>   6dd8b1a0b6cb ("arm64: mte: Dump the MTE tags in the core file")
> 
> from the arm64 tree.

Yikes, this is quite a mess. Liam -- how would you like to resolve this?

Will

  reply	other threads:[~2022-02-17 19:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  8:18 linux-next: build failure after merge of the maple tree Stephen Rothwell
2022-02-17 19:24 ` Will Deacon [this message]
2022-02-18  1:46   ` Liam Howlett
2022-02-18  2:37     ` [PATCH] arm64: Change elfcore for_each_mte_vma() to use VMA iterator Liam Howlett
2022-02-21 18:06       ` Catalin Marinas
2022-02-22 14:26         ` Liam Howlett
2022-02-22 16:20           ` Will Deacon
2022-02-22 17:26             ` Catalin Marinas
2022-02-22 18:54               ` Liam Howlett
2022-02-23  9:39                 ` Catalin Marinas
2022-02-23 13:57                   ` Liam Howlett
2022-02-23 11:37                 ` Catalin Marinas
2022-02-23 14:11                   ` Liam Howlett
2022-02-24  2:00                     ` Liam Howlett
2022-02-25 15:50       ` Will Deacon
2022-02-17  8:27 linux-next: build failure after merge of the maple tree Stephen Rothwell
2022-02-18  2:14 ` Liam Howlett
2022-02-23  0:45 broonie
2022-02-23  2:32 ` Liam Howlett

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=20220217192434.GA11800@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=liam.howlett@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.