From: Kees Cook <keescook@chromium.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Adam Borowski <kilobyte@angband.pl>, Dave Mielke <Dave@mielke.cc>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-console@vger.kernel.org
Subject: Re: [PATCH 0/3] follow-up to the unicode vt console series
Date: Wed, 18 Jul 2018 07:04:56 -0700 [thread overview]
Message-ID: <CAGXu5jLkgA2gLPM3cMwvTgGcBR3MBRHtJjO-EsTgpz5uqgHsaw@mail.gmail.com> (raw)
In-Reply-To: <20180718010242.5254-1-nicolas.pitre@linaro.org>
Hi Nicolas,
On Tue, Jul 17, 2018 at 6:02 PM, Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
> This is a follow-up series with 3 patches in response to the following
> messages respectively:
>
> http://lkml.kernel.org/r/20180628123803.GA22045@kroah.com
>
> http://lkml.kernel.org/r/CAGXu5j+KLvJ-n_QRrfq15E8iO_rqfpp+K7PDAZHZMHcemy9y7g@mail.gmail.com
>
> http://lkml.kernel.org/r/CAMuHMdUmC+uiKTEMotB83A86E1wEYrNF2qPf3kDACaW27D_NbA@mail.gmail.com
>
> Those patches were tested on top of previous patches already in tty-next.
> Please include in tty-next before next merge window.
>
> Patch #1 was posted before. Only difference is that it now uses rate
> limited printing.
>
> Patch #2 is new, however it has been tested with the validation code
> provided by patch #1. This also fixes a security issue.
>
> Patch #3 is new and trivial.
>
> Diffstat:
>
> Documentation/admin-guide/devices.txt | 16 +++++---
> drivers/tty/vt/vt.c | 57 +++++++++++++++++++++++++----
> 2 files changed, 59 insertions(+), 14 deletions(-)
Thanks for fixing the VLA! :)
-Kees
--
Kees Cook
Pixel Security
prev parent reply other threads:[~2018-07-18 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 1:02 [PATCH 0/3] follow-up to the unicode vt console series Nicolas Pitre
2018-07-18 1:02 ` [PATCH 1/3] vt: avoid a VLA in the unicode screen scroll function Nicolas Pitre
2018-07-18 1:48 ` Adam Borowski
2018-07-18 2:54 ` Nicolas Pitre
2018-07-19 4:05 ` Nicolas Pitre
2018-07-21 7:20 ` [PATCH v2 " Greg Kroah-Hartman
2018-07-18 1:02 ` [PATCH 2/3] vt: coherence validation code for the unicode screen buffer Nicolas Pitre
2018-07-18 1:02 ` [PATCH 3/3] vt: add /dev/vcsu* to devices.txt Nicolas Pitre
2018-07-18 7:25 ` Geert Uytterhoeven
2018-07-18 14:04 ` Kees Cook [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=CAGXu5jLkgA2gLPM3cMwvTgGcBR3MBRHtJjO-EsTgpz5uqgHsaw@mail.gmail.com \
--to=keescook@chromium.org \
--cc=Dave@mielke.cc \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kilobyte@angband.pl \
--cc=linux-console@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=samuel.thibault@ens-lyon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).