public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Danilo Krummrich <dakr@kernel.org>,
	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 s390 tree
Date: Thu, 8 Aug 2024 13:58:36 +1000	[thread overview]
Message-ID: <20240808135836.740effac@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 4068 bytes --]

Hi all,

After merging the s390 tree, today's linux-next build (s390 defconfig)
failed like this:

In file included from include/linux/percpu.h:5,
                 from include/linux/percpu_counter.h:14,
                 from include/linux/mm_types.h:21,
                 from include/linux/ptdump.h:6,
                 from arch/s390/mm/dump_pagetables.c:3:
arch/s390/mm/dump_pagetables.c: In function 'add_marker':
include/linux/slab.h:848:61: error: too many arguments to function 'kvrealloc_noprof'
  848 | #define kvrealloc(...)                          alloc_hooks(kvrealloc_noprof(__VA_ARGS__))
      |                                                             ^~~~~~~~~~~~~~~~
include/linux/alloc_tag.h:206:16: note: in definition of macro 'alloc_hooks_tag'
  206 |         typeof(_do_alloc) _res = _do_alloc;                             \
      |                ^~~~~~~~~
include/linux/slab.h:848:49: note: in expansion of macro 'alloc_hooks'
  848 | #define kvrealloc(...)                          alloc_hooks(kvrealloc_noprof(__VA_ARGS__))
      |                                                 ^~~~~~~~~~~
arch/s390/mm/dump_pagetables.c:259:27: note: in expansion of macro 'kvrealloc'
  259 |                 markers = kvrealloc(markers, oldsize, newsize, GFP_KERNEL);
      |                           ^~~~~~~~~
In file included from include/linux/fs.h:45,
                 from include/linux/seq_file.h:11,
                 from arch/s390/mm/dump_pagetables.c:4:
include/linux/slab.h:846:7: note: declared here
  846 | void *kvrealloc_noprof(const void *p, size_t size, gfp_t flags)
      |       ^~~~~~~~~~~~~~~~
include/linux/slab.h:848:61: error: too many arguments to function 'kvrealloc_noprof'
  848 | #define kvrealloc(...)                          alloc_hooks(kvrealloc_noprof(__VA_ARGS__))
      |                                                             ^~~~~~~~~~~~~~~~
include/linux/alloc_tag.h:206:34: note: in definition of macro 'alloc_hooks_tag'
  206 |         typeof(_do_alloc) _res = _do_alloc;                             \
      |                                  ^~~~~~~~~
include/linux/slab.h:848:49: note: in expansion of macro 'alloc_hooks'
  848 | #define kvrealloc(...)                          alloc_hooks(kvrealloc_noprof(__VA_ARGS__))
      |                                                 ^~~~~~~~~~~
arch/s390/mm/dump_pagetables.c:259:27: note: in expansion of macro 'kvrealloc'
  259 |                 markers = kvrealloc(markers, oldsize, newsize, GFP_KERNEL);
      |                           ^~~~~~~~~
include/linux/slab.h:846:7: note: declared here
  846 | void *kvrealloc_noprof(const void *p, size_t size, gfp_t flags)
      |       ^~~~~~~~~~~~~~~~

Caused by commit

  d0e7915d2ad3 ("s390/mm/ptdump: Generate address marker array dynamically")

interacting with commit

  d4a913add37d ("mm: kvmalloc: align kvrealloc() with krealloc()")

from the mm-unstable branch of the mm tree.

I have applied the following merge fix patch.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 8 Aug 2024 13:50:39 +1000
Subject: [PATCH] fixup for "s390/mm/ptdump: Generate address marker array dynamically"

interacting with "mm: kvmalloc: align kvrealloc() with krealloc()"
from the mm tree.

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 arch/s390/mm/dump_pagetables.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/s390/mm/dump_pagetables.c b/arch/s390/mm/dump_pagetables.c
index 9e2dc42143b3..fa54f3bc0c8d 100644
--- a/arch/s390/mm/dump_pagetables.c
+++ b/arch/s390/mm/dump_pagetables.c
@@ -256,7 +256,7 @@ static int add_marker(unsigned long start, unsigned long end, const char *name)
 	if (!oldsize)
 		markers = kvmalloc(newsize, GFP_KERNEL);
 	else
-		markers = kvrealloc(markers, oldsize, newsize, GFP_KERNEL);
+		markers = kvrealloc(markers, newsize, GFP_KERNEL);
 	if (!markers)
 		goto error;
 	markers[markers_cnt].is_start = 1;
-- 
2.43.0

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-08-08  3:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08  3:58 Stephen Rothwell [this message]
2024-09-11  8:09 ` linux-next: build failure after merge of the s390 tree Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-01-10  9:22 Stephen Rothwell
2023-01-10 14:22 ` Heiko Carstens
2011-05-20  1:56 Stephen Rothwell
2011-05-20  9:24 ` Martin Schwidefsky

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=20240808135836.740effac@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=borntraeger@de.ibm.com \
    --cc=dakr@kernel.org \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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