From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: Jinpu Wang <jinpuwang@gmail.com>, Sasha Levin <sashal@kernel.org>,
"v3.14+, only the raid10 part" <stable@vger.kernel.org>
Subject: Re: [stable-4.19 0/4] CVE-2019-3900 fixes
Date: Fri, 2 Aug 2019 09:16:04 +0200 [thread overview]
Message-ID: <20190802071604.GA26174@kroah.com> (raw)
In-Reply-To: <20190802071342.GA25871@kroah.com>
On Fri, Aug 02, 2019 at 09:13:42AM +0200, Greg Kroah-Hartman wrote:
>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
>
> On Fri, Aug 02, 2019 at 09:02:01AM +0200, Nikola Ciprich wrote:
> > Hi,
> >
> > just wanted to ask about the status of those? I'm testing patches on top
> > of 4.19.60, not sure about how can I test if the problem is fixed, but at
> > least nothing seems to be broken so far..
>
> We wanted to get some verification that the issues were really fixed by
> these patches. If no one knows how to test them, then odds are they are
> not vulnerable, right? :)
Ok, snarkyness aside, let me look at these today and queue them up.
They have been sitting here for a while and they would be good to get
merged...
thanks,
greg k-h
next prev parent reply other threads:[~2019-08-02 7:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 13:03 [stable-4.19 0/4] CVE-2019-3900 fixes Jack Wang
2019-07-22 13:03 ` [stable-4.19 1/4] vhost: introduce vhost_exceeds_weight() Jack Wang
2019-07-22 13:03 ` [stable-4.19 2/4] vhost_net: fix possible infinite loop Jack Wang
2019-07-22 13:03 ` [stable-4.19 3/4] vhost: vsock: add weight support Jack Wang
2019-07-22 13:03 ` [stable-4.19 4/4] vhost: scsi: " Jack Wang
2019-07-22 15:42 ` [stable-4.19 0/4] CVE-2019-3900 fixes Sasha Levin
2019-07-23 9:59 ` Jinpu Wang
2019-08-02 7:02 ` Nikola Ciprich
2019-08-02 7:13 ` Greg Kroah-Hartman
2019-08-02 7:16 ` Greg Kroah-Hartman [this message]
2019-08-02 7:27 ` Greg KH
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=20190802071604.GA26174@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jinpuwang@gmail.com \
--cc=nikola.ciprich@linuxbox.cz \
--cc=sashal@kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).