From: John Ogness <john.ogness@linutronix.de>
To: gregkh@linuxfoundation.org, gregkh@linuxfoundation.org,
pmladek@suse.com, sergey.senozhatsky@gmail.com,
stable@vger.kernel.org
Cc: stable-commits@vger.kernel.org
Subject: Re: Patch "printk: fix buffer overflow potential for print_text()" has been added to the 5.10-stable tree
Date: Sun, 24 Jan 2021 21:39:33 +0106 [thread overview]
Message-ID: <87zh0ym5wi.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <1611495423221153@kroah.com>
Hi Greg,
On 2021-01-24, <gregkh@linuxfoundation.org> wrote:
> This is a note to let you know that I've just added the patch titled
>
> printk: fix buffer overflow potential for print_text()
We just learned that this patch introduces a new problem. I have just
posted a patch to fix the new problem:
https://lkml.kernel.org/r/20210124202728.4718-1-john.ogness@linutronix.de
You may want to hold off on applying the first fix until the second fix
has been accepted. Then you can apply both.
John Ogness
next parent reply other threads:[~2021-01-24 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1611495423221153@kroah.com>
2021-01-24 20:33 ` John Ogness [this message]
2021-01-25 14:58 ` Patch "printk: fix buffer overflow potential for print_text()" has been added to the 5.10-stable tree Greg KH
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=87zh0ym5wi.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=stable-commits@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.