From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Masami Hiramatsu (Google) <mhiramat@kernel.org>,
Qiang Zhang <qiang4.zhang@intel.com>,
Yuntao Wang <ytcoode@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] bootconfig: Fixes for v6.9-rc4
Date: Fri, 19 Apr 2024 14:32:51 +0900 [thread overview]
Message-ID: <20240419143251.35ba9e253bb5fa07ad9b71dc@kernel.org> (raw)
Hi Linus,
Bootconfig fixes for v6.9-rc4:
- Fix potential static_command_line buffer overrun. Currently we allocate
the memory for static_command_line based on "boot_command_line", but it
will copy "command_line" into it. So we use the length of "command_line"
instead of "boot_command_line" (as previously we did).
- Use memblock_free_late() in xbc_exit() instead of memblock_free() after
the buddy system is initialized.
- Fix a kerneldoc warning.
Please pull the latest bootconfig-fixes-v6.9-rc4 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
bootconfig-fixes-v6.9-rc4
Tag SHA1: 7b37e0d614e8989ec4163385fe76fff290f005b9
Head SHA1: 298b871cd55a607037ac8af0011b9fdeb54c1e65
Masami Hiramatsu (Google) (1):
bootconfig: Fix the kerneldoc of _xbc_exit()
Qiang Zhang (1):
bootconfig: use memblock_free_late to free xbc memory to buddy
Yuntao Wang (1):
init/main.c: Fix potential static_command_line memory overflow
----
include/linux/bootconfig.h | 7 ++++++-
init/main.c | 2 ++
lib/bootconfig.c | 22 +++++++++++++---------
3 files changed, 21 insertions(+), 10 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2024-04-19 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 5:32 Masami Hiramatsu [this message]
2024-04-19 17:04 ` [GIT PULL] bootconfig: Fixes for v6.9-rc4 pr-tracker-bot
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=20240419143251.35ba9e253bb5fa07ad9b71dc@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang4.zhang@intel.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=ytcoode@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