From: Thorsten Blum <blum@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Breno Leitao <leitao@debian.org>,
Christian Brauner <brauner@kernel.org>,
Sang-Heon Jeon <ekffu200098@gmail.com>,
Wilson Felipe Pereira <wfelipe@google.com>,
Ryan Roberts <ryan.roberts@arm.com>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>
Cc: Thorsten Blum <blum@kernel.org>, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] init: Combine blacklist entry allocations in initcall_blacklist()
Date: Sun, 15 Nov 2026 15:23:21 +0100 [thread overview]
Message-ID: <20261115142321.96774-4-blum@kernel.org> (raw)
In-Reply-To: <20261115142321.96774-3-blum@kernel.org>
Use a flexible array member for the function name and allocate it
together with the blacklist entry. This removes the pointer and saves
one allocation call per blacklist entry.
Signed-off-by: Thorsten Blum <blum@kernel.org>
---
init/main.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/init/main.c b/init/main.c
index db8fb6ebe830..da10f08037ef 100644
--- a/init/main.c
+++ b/init/main.c
@@ -28,6 +28,7 @@
#include <linux/init.h>
#include <linux/initrd.h>
#include <linux/memblock.h>
+#include <linux/overflow.h>
#include <linux/acpi.h>
#include <linux/bootconfig.h>
#include <linux/console.h>
@@ -1266,7 +1267,7 @@ static void __init do_ctors(void)
#ifdef CONFIG_KALLSYMS
struct blacklist_entry {
struct list_head next;
- char *buf;
+ char buf[];
};
static __initdata_or_module LIST_HEAD(blacklisted_initcalls);
@@ -1281,8 +1282,8 @@ static int __init initcall_blacklist(char *str)
size_t buf_size = strlen(str_entry) + 1;
pr_debug("blacklisting initcall %s\n", str_entry);
- entry = memblock_alloc_or_panic(sizeof(*entry), SMP_CACHE_BYTES);
- entry->buf = memblock_alloc_or_panic(buf_size, SMP_CACHE_BYTES);
+ entry = memblock_alloc_or_panic(struct_size(entry, buf, buf_size),
+ SMP_CACHE_BYTES);
strscpy(entry->buf, str_entry, buf_size);
list_add(&entry->next, &blacklisted_initcalls);
}
prev parent reply other threads:[~2026-11-15 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 14:23 [PATCH 1/2] init: Use strscpy() " Thorsten Blum
2026-11-15 14:23 ` Thorsten Blum [this message]
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=20261115142321.96774-4-blum@kernel.org \
--to=blum@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=ekffu200098@gmail.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=wfelipe@google.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
all inboxes | Powered by JetHome®