From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Slaby <jslaby@suse.com>
Cc: yebin10@huawei.com, stable@vger.kernel.org
Subject: Re: patch "vt: fix use after free in function "vc_do_resize"" added to tty-testing
Date: Tue, 24 Mar 2020 13:31:33 +0100 [thread overview]
Message-ID: <20200324123133.GC2348009@kroah.com> (raw)
In-Reply-To: <2770bbb6-f49b-f0a4-b7ee-7615609f3724@suse.com>
On Tue, Mar 24, 2020 at 12:47:19PM +0100, Jiri Slaby wrote:
> On 24. 03. 20, 12:31, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > vt: fix use after free in function "vc_do_resize"
>
> I lost track about this one, but isn't this the patch which was
> withdrawn in favor of another patch really fixing the problem?
Was it? I didn't think so. But I have no idea. I'll go drop this now
and wait for confirmation from Ye.
thanks,
greg k-h
prev parent reply other threads:[~2020-03-24 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 11:31 patch "vt: fix use after free in function "vc_do_resize"" added to tty-testing gregkh
2020-03-24 11:47 ` Jiri Slaby
2020-03-24 12:31 ` Greg KH [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=20200324123133.GC2348009@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=stable@vger.kernel.org \
--cc=yebin10@huawei.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;
as well as URLs for NNTP newsgroup(s).