From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Jiri Slaby <jirislaby@kernel.org>, linux-serial@vger.kernel.org
Subject: Re: [PATCH] vt: fix unicode buffer corruption when deleting characters
Date: Thu, 29 Feb 2024 22:51:57 +0100 [thread overview]
Message-ID: <2024022936-chloride-concert-12a6@gregkh> (raw)
In-Reply-To: <88n6qo5r-2986-r273-9n4p-pr77q314727r@syhkavp.arg>
On Thu, Feb 29, 2024 at 04:05:51PM -0500, Nicolas Pitre wrote:
> This is the same issue that was fixed for the VGA text buffer in
> commit 39cdb68c64d8 ("vt: fix memory overlapping when deleting chars
> in the buffer"). The cure is also the same.
Please spell out what the "cure" is here, so we don't have to do and
look up another commit somewhere else :)
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-29 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 21:05 [PATCH] vt: fix unicode buffer corruption when deleting characters Nicolas Pitre
2024-02-29 21:51 ` Greg Kroah-Hartman [this message]
2024-02-29 22:10 ` Nicolas Pitre
2024-03-02 20:45 ` Greg Kroah-Hartman
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=2024022936-chloride-concert-12a6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nico@fluxnic.net \
/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