From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthew Wilcox <willy@infradead.org>,
Liam Howlett <liam.howlett@oracle.com>
Cc: Hugh Dickins <hughd@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Vasily Gorbik <gor@linux.ibm.com>,
"maple-tree@lists.infradead.org" <maple-tree@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Subject: linux-next: build failure after merge of the folio tree
Date: Mon, 28 Feb 2022 23:53:56 +1100 [thread overview]
Message-ID: <20220228235356.5aca3e03@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]
Hi all,
After merging the folio tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
mm/mmap.c: In function 'do_mas_align_munmap':
mm/mmap.c:2375:25: error: implicit declaration of function 'munlock_vma_pages_all'; did you mean 'munlock_vma_page'? [-Werror=implicit-function-declaration]
2375 | munlock_vma_pages_all(next);
| ^~~~~~~~~~~~~~~~~~~~~
| munlock_vma_page
mm/mmap.c: In function 'do_brk_munmap':
mm/mmap.c:2908:17: error: implicit declaration of function 'munlock_vma_pages_range'; did you mean 'count_vma_pages_range'? [-Werror=implicit-function-declaration]
2908 | munlock_vma_pages_range(&unmap, newbrk, oldbrk);
| ^~~~~~~~~~~~~~~~~~~~~~~
| count_vma_pages_range
Caused by commits
a213e5cf71cb ("mm/munlock: delete munlock_vma_pages_all(), allow oomreap")
34b6792380ce ("mm/munlock: mlock_pte_range() when mlocking or munlocking")
interacting with commits
99f86dff3df6 ("mm/mmap: Change do_brk_flags() to expand existing VMA and add do_brk_munmap()")
04552dc1edc5 ("mm: Remove the vma linked list")
from the maple tree.
Given other feedback about the maple tree, I have dropped it for today.
I am not sure what effect this will have on Andrew's patch series, but
I guess I will find out shortly :-(
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2022-02-28 12:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220228235356.5aca3e03@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hughd@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=maple-tree@lists.infradead.org \
--cc=willy@infradead.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