Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Markus Probst <markus.probst@posteo.de>, linux-serial@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>, Jiri Slaby <jirislaby@kernel.org>,
	linux-kernel@vger.kernel.org, Joshua Rogers <linux@joshua.hu>,
	stable <stable@kernel.org>
Subject: Re: [PATCH 0/2] serdev: Some small serdev bugfixes found by code scans
Date: Fri, 31 Jul 2026 10:14:42 +0200	[thread overview]
Message-ID: <2026073133-eligibly-operation-dbd8@gregkh> (raw)
In-Reply-To: <20260731-aisle-tty-serdev-v1-0-2401a3189327@linuxfoundation.org>

On Fri, Jul 31, 2026 at 10:06:08AM +0200, Greg Kroah-Hartman wrote:
> Joshua at AISLE has been kind enough to run a bunch of scans on the
> tty/serial code and here are two minor fixes for the vt code that the

s/vt/serdev/

{sigh}

      parent reply	other threads:[~2026-07-31  8:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  8:06 [PATCH 0/2] serdev: Some small serdev bugfixes found by code scans Greg Kroah-Hartman
2026-07-31  8:06 ` [PATCH 1/2] serdev: fix race between tty-port unregister and in-flight callbacks Greg Kroah-Hartman
2026-07-31 11:30   ` Markus Probst
2026-07-31 12:01     ` Greg Kroah-Hartman
2026-07-31 12:43       ` Markus Probst
2026-07-31  8:06 ` [PATCH 2/2] serdev: use tty_port_tty_get() in ttyport_write_buf() to prevent UAF Greg Kroah-Hartman
2026-07-31  8:24   ` Jiri Slaby
2026-07-31  8:28     ` Greg Kroah-Hartman
2026-07-31 13:00   ` Markus Probst
2026-07-31 13:22     ` Greg Kroah-Hartman
2026-07-31 13:30       ` Markus Probst
2026-07-31  8:14 ` 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=2026073133-eligibly-operation-dbd8@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux@joshua.hu \
    --cc=markus.probst@posteo.de \
    --cc=robh@kernel.org \
    --cc=stable@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