From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kees Cook <kees@kernel.org>, Christian Brauner <brauner@kernel.org>
Cc: Mateusz Guzik <mjguzik@gmail.com>, Brian Mak <makb@juniper.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the execve tree
Date: Mon, 24 Feb 2025 17:40:47 +1100 [thread overview]
Message-ID: <20250224174047.7d1bd6e4@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2193 bytes --]
Hi all,
After merging the execve tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/coredump.c: In function 'dump_vma_snapshot':
fs/coredump.c:1301:45: error: too few arguments to function 'get_dump_page'
1301 | struct page *page = get_dump_page(addr);
| ^~~~~~~~~~~~~
In file included from fs/coredump.c:6:
include/linux/mm.h:2620:14: note: declared here
2620 | struct page *get_dump_page(unsigned long addr, int *locked);
| ^~~~~~~~~~~~~
Caused by commit
ff41385709f0 ("coredump: Only sort VMAs when truncating or core_sort_vma sysctl is set")
interacting with commit
d6ff4c8f6522 ("fs: avoid mmap sem relocks when coredumping with many missing pages")
from the vfs-brauner tree.
I did the obvious (but probably wrong fix up below).
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 24 Feb 2025 17:27:25 +1100
Subject: [PATCH] fix up for "coredump: Only sort VMAs when truncating or
core_sort_vma sysctl is set"
interacting with commit
d6ff4c8f6522 ("fs: avoid mmap sem relocks when coredumping with many missing pages")
from the vfs-brauner tree.
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
fs/coredump.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/coredump.c b/fs/coredump.c
index 723c1ae9d2f4..eb75cd30862d 100644
--- a/fs/coredump.c
+++ b/fs/coredump.c
@@ -1243,6 +1243,7 @@ static bool dump_vma_snapshot(struct coredump_params *cprm)
VMA_ITERATOR(vmi, mm, 0);
int i = 0;
size_t sparse_vma_dump_size = 0;
+ int locked = 0;
/*
* Once the stack expansion code is fixed to not change VMA bounds
@@ -1298,7 +1299,7 @@ static bool dump_vma_snapshot(struct coredump_params *cprm)
/* Subtract zero pages from the sparse_vma_dump_size. */
for (addr = m->start; addr < m->start + m->dump_size; addr += PAGE_SIZE) {
- struct page *page = get_dump_page(addr);
+ struct page *page = get_dump_page(addr, &locked);
if (!page)
sparse_vma_dump_size -= PAGE_SIZE;
--
2.45.2
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-02-24 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 6:40 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-03 2:35 linux-next: build failure after merge of the execve tree Stephen Rothwell
2023-10-04 2:50 ` Kees Cook
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=20250224174047.7d1bd6e4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brauner@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=makb@juniper.net \
--cc=mjguzik@gmail.com \
/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