From: Sang-Heon Jeon <ekffu200098@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: John Ogness <john.ogness@linutronix.de>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH] printk: use memblock_alloc_raw() in setup_log_buf()
Date: Wed, 16 Sep 2026 00:02:37 +0900 [thread overview]
Message-ID: <20260915150240.390967-1-ekffu200098@gmail.com> (raw)
setup_log_buf() allocates the prb_desc and printk_info arrays with
memblock_alloc(), which returns zero-initialized memory. prb_init() then
zeroes both arrays, and nothing uses them in between.
So allocate both arrays with memblock_alloc_raw() instead.
No functional change.
Signed-off-by: Sang-Heon Jeon <ekffu200098@gmail.com>
---
kernel/printk/printk.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 3fcdf4b4e2e5..fe98d6a86e4a 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -1197,7 +1197,7 @@ void __init setup_log_buf(int early)
}
new_descs_size = new_descs_count * sizeof(struct prb_desc);
- new_descs = memblock_alloc(new_descs_size, LOG_ALIGN);
+ new_descs = memblock_alloc_raw(new_descs_size, LOG_ALIGN);
if (unlikely(!new_descs)) {
pr_err("log_buf_len: %zu desc bytes not available\n",
new_descs_size);
@@ -1205,7 +1205,7 @@ void __init setup_log_buf(int early)
}
new_infos_size = new_descs_count * sizeof(struct printk_info);
- new_infos = memblock_alloc(new_infos_size, LOG_ALIGN);
+ new_infos = memblock_alloc_raw(new_infos_size, LOG_ALIGN);
if (unlikely(!new_infos)) {
pr_err("log_buf_len: %zu info bytes not available\n",
new_infos_size);
--
2.43.0
reply other threads:[~2026-09-15 15:02 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=20260915150240.390967-1-ekffu200098@gmail.com \
--to=ekffu200098@gmail.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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®