From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: Jinpu Wang <jinpuwang@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>, "v3.14+,
only the raid10 part" <stable@vger.kernel.org>,
Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Subject: Re: [stable-4.19 0/4] CVE-2019-3900 fixes
Date: Fri, 2 Aug 2019 09:02:01 +0200 [thread overview]
Message-ID: <20190802070201.GA18798@pcnci.linuxbox.cz> (raw)
In-Reply-To: <CAD9gYJ+xhujXEHVNAEB5EUO7vwkXuZeU-xf0+g049uk8ucP_tA@mail.gmail.com>
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..
BR
nik
On Tue, Jul 23, 2019 at 11:59:16AM +0200, Jinpu Wang wrote:
> Sasha Levin <sashal@kernel.org> 于2019年7月22日周一 下午5:42写道:
> >
> > On Mon, Jul 22, 2019 at 03:03:09PM +0200, Jack Wang wrote:
> > >Hi, Greg, hi Sasha,
> > >
> > >I noticed the fixes for CVE-2019-3900 are only backported to 4.14.133+,
> > >but not to 4.19, also 5.1, fixes have been included in 5.2.
> > >
> > >So I backported to 4.19, only compiles fine, no functional tests.
> > >
> > >Please review, and consider to include in next release.
> >
> > Thanks Jack. It'll be great if someone can test it and confirm it fixes
> > the issue (and nothing else breaks).
> >
> Agree, thanks
> > --
> > Thanks,
> > Sasha
>
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28.rijna 168, 709 00 Ostrava
tel.: +420 591 166 214
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
next prev parent reply other threads:[~2019-08-02 7:12 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 [this message]
2019-08-02 7:13 ` Greg Kroah-Hartman
2019-08-02 7:16 ` Greg Kroah-Hartman
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=20190802070201.GA18798@pcnci.linuxbox.cz \
--to=nikola.ciprich@linuxbox.cz \
--cc=gregkh@linuxfoundation.org \
--cc=jinpuwang@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.