From: Calvin Owens <calvin@wbinvd.org>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, Roman Gushchin <roman.gushchin@linux.dev>,
David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@gentwo.org>, Hao Li <hao.li@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Harry Yoo <harry@kernel.org>, Vlastimil Babka <vbabka@kernel.org>
Subject: [PATCH next-20260615] mm/slab: Fix build error due to extra argument
Date: Mon, 15 Jun 2026 09:32:32 -0700 [thread overview]
Message-ID: <8a5c513e810a216ca221bbec94c96ffbf65da4be.1781540225.git.calvin@wbinvd.org> (raw)
mm/slub.c:5553:30: error: too many arguments to function call, expected 5, have 6
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ~~~~~~~~~~~~~~~~~
Fix by removing the nonexistent size argument.
Closes: https://lore.kernel.org/all/178153914528.15282.16770125845520023465@330cfa3079ca/
Signed-off-by: Calvin Owens <calvin@wbinvd.org>
---
I needed to test -next this morning, so passing this along, but please
don't go to any extra trouble to use it or credit me if you already
fixed it :)
mm/slub.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/slub.c b/mm/slub.c
index b1de95046b0b..7660f7fa0b2c 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -5549,7 +5549,7 @@ void *__kmalloc_flags_noprof(DECL_TOKEN_PARAMS(size, token), gfp_t flags,
};
if (alloc_flags_allow_spinning(alloc_flags)) {
- return __do_kmalloc_node(size, NULL, flags, node,
+ return __do_kmalloc_node(NULL, flags, node,
PASS_TOKEN_PARAM(token), &ac);
} else {
return __kmalloc_nolock_noprof(PASS_TOKEN_PARAMS(size, token),
--
2.53.0
next reply other threads:[~2026-06-15 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 16:32 Calvin Owens [this message]
2026-06-15 17:12 ` Calvin Owens
2026-06-15 18:10 ` Calvin Owens
2026-06-15 18:33 ` Vlastimil Babka (SUSE)
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=8a5c513e810a216ca221bbec94c96ffbf65da4be.1781540225.git.calvin@wbinvd.org \
--to=calvin@wbinvd.org \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@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
all inboxes | Powered by JetHome®