[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180329113024.6cc18340@vento.lan>
Date: Thu, 29 Mar 2018 11:30:24 -0300
From: Mauro Carvalho Chehab <mchehab@...pensource.com>
To: Inki Dae <inki.dae@...sung.com>
Cc: Linux Media Mailing List <linux-media@...r.kernel.org>,
stable@...r.kernel.org, Greg KH <gregkh@...uxfoundation.org>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Seung-Woo Kim <sw0312.kim@...sung.com>,
Brian Warner <brian.warner@...sung.com>
Subject: Re: [PATCH for v3.18 00/18] Backport CVE-2017-13166 fixes to Kernel
3.18
Em Thu, 29 Mar 2018 08:22:08 +0900
Inki Dae <inki.dae@...sung.com> escreveu:
> Hi Mauro,
>
> 2018년 03월 29일 03:12에 Mauro Carvalho Chehab 이(가) 쓴 글:
> > Hi Greg,
> >
> > Those are the backports meant to solve CVE-2017-13166 on Kernel 3.18.
> >
> > It contains two v4l2-ctrls fixes that are required to avoid crashes
> > at the test application.
> >
> > I wrote two patches myself for Kernel 3.18 in order to solve some
> > issues specific for Kernel 3.18 with aren't needed upstream.
> > one is actually a one-line change backport. The other one makes
> > sure that both 32-bits and 64-bits version of some ioctl calls
> > will return the same value for a reserved field.
> >
> > I noticed an extra bug while testing it, but the bug also hits upstream,
> > and should be backported all the way down all stable/LTS versions.
> > So, I'll send it the usual way, after merging upsream.
>
> Really thanks for doing this. :) There would be many users who use Linux-3.18 for their products yet.
Anytime!
Please let me know if you find any issues with those backports.
Regards,
Mauro
Powered by blists - more mailing lists