From: John Ogness <john.ogness@linutronix.de>
To: stable@vger.kernel.org
Cc: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: printk: buffer overflow fixes
Date: Tue, 26 Jan 2021 00:30:24 +0106 [thread overview]
Message-ID: <878s8g38if.fsf@jogness.linutronix.de> (raw)
Hello stable,
The following printk patches fixing a buffer overflow potential in 5.10
are now available in Linus' tree:
f0e386ee0c0b71ea6f7238506a4d0965a2dbef11 ("printk: fix buffer overflow
potential for print_text()")
08d60e5999540110576e7c1346d486220751b7f9 ("printk: fix string
termination for record_print_text()")
The first one (f0e386ee0c0b) was already queued up for 5.10-stable but I
requested it not be applied until this second one was accepted. Now they
are both accepted and both should be applied. Thanks.
John Ogness
reply other threads:[~2021-01-25 23:25 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=878s8g38if.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=stable@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