From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sven Schnelle <svens@linux.ibm.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v2 0/2] fix out-of-bounds access when specifying invalid console
Date: Thu, 19 Jan 2023 15:04:49 +0100 [thread overview]
Message-ID: <Y8lOAVTBlay2QrYC@kroah.com> (raw)
In-Reply-To: <yt9dh6x6n4tq.fsf@linux.ibm.com>
On Wed, Jan 04, 2023 at 08:20:49AM +0100, Sven Schnelle wrote:
> Sven Schnelle <svens@linux.ibm.com> writes:
>
> > Hi,
> >
> > these two patches fix a crash in the tty driver when a user specifies an
> > invalid console like 'console=tty3000'. The first patch adds a check to
> > tty_driver_lookup_tty(), the second one prevents that such a console gets
> > registered in the vt driver.
> >
> > Changes in v2:
> > - trim commit message in first patch
> > - add second patch as suggested by Jiri Slaby
> >
> > Sven Schnelle (2):
> > tty: fix out-of-bounds access in tty_driver_lookup_tty()
> > tty/vt: prevent registration of console with invalid number
> >
> > drivers/tty/tty_io.c | 8 +++++---
> > drivers/tty/vt/vt.c | 6 ++++++
> > 2 files changed, 11 insertions(+), 3 deletions(-)
>
> Gentle ping... I couldn't find that this was applied anywhere?
Sorry, still digging out of a lot of patches...
prev parent reply other threads:[~2023-01-19 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 11:27 [PATCH v2 0/2] fix out-of-bounds access when specifying invalid console Sven Schnelle
2022-12-09 11:27 ` [PATCH v2 1/2] tty: fix out-of-bounds access in tty_driver_lookup_tty() Sven Schnelle
2022-12-09 11:27 ` [PATCH v2 2/2] tty/vt: prevent registration of console with invalid number Sven Schnelle
2023-01-04 7:20 ` [PATCH v2 0/2] fix out-of-bounds access when specifying invalid console Sven Schnelle
2023-01-04 8:26 ` Greg Kroah-Hartman
2023-01-19 14:04 ` Greg Kroah-Hartman [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=Y8lOAVTBlay2QrYC@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=borntraeger@de.ibm.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.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