From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Seung-Woo Kim <sw0312.kim@samsung.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Inki Dae <inki.dae@samsung.com>
Subject: Re: Linux 3.18.102
Date: Tue, 27 Mar 2018 08:30:54 -0300 [thread overview]
Message-ID: <20180327083054.1d9b7796@vento.lan> (raw)
In-Reply-To: <5AB9F365.2030309@samsung.com>
Em Tue, 27 Mar 2018 16:31:49 +0900
Seung-Woo Kim <sw0312.kim@samsung.com> escreveu:
> On 2018년 03월 27일 16:05, Greg KH wrote:
> > On Tue, Mar 27, 2018 at 10:40:33AM +0900, Seung-Woo Kim wrote:
> >> Hello,
> >>
> >> Until 3.18.102, it looks like following patch series for v4l2 seems missed.
> >>
> >> 273caa2 media: v4l2-compat-ioctl32.c: make ctrl_is_pointer work for subdevs
> >> a1dfb4c media: v4l2-compat-ioctl32.c: refactor compat ioctl32 logic
> >> d83a824 media: v4l2-compat-ioctl32.c: don't copy back the result for
> >> certain errors
> >> 169f24c media: v4l2-compat-ioctl32.c: drop pr_info for unknown buffer type
> >> a751be5 media: v4l2-compat-ioctl32.c: copy clip list in put_v4l2_window32
> >> b8c601e media: v4l2-compat-ioctl32.c: fix ctrl_is_pointer
> >> 8ed5a59 media: v4l2-compat-ioctl32.c: copy m.userptr in put_v4l2_plane32
> >> 333b1e9 media: v4l2-compat-ioctl32.c: avoid sizeof(type)
> >> 486c521 media: v4l2-compat-ioctl32.c: move 'helper' functions to
> >> __get/put_v4l2_format32
> >> b7b957d media: v4l2-compat-ioctl32.c: fix the indentation
> >> 3ee6d04 media: v4l2-compat-ioctl32.c: add missing VIDIOC_PREPARE_BUF
> >> 181a4a2 media: v4l2-ioctl.c: don't copy back the result for -ENOTTY
> >
> > That is correct.
> >
> >> Any plan to apply the series?
> >
> > Do you have a backported version of this series that will apply to that
> > kernel tree? If so, I'll be glad to apply it but I'm pretty sure the
> > reason I did not apply them was because they did not apply correctly.
>
> I dit not do it myself. I just checked the series is applied on other
> stable trees.
Backporting it from Kernel 4.1 is quite simple. Just two patches
have trivial conflicts.
I did a quick backport at:
https://git.linuxtv.org/mchehab/experimental.git/log/?h=v3.18.102%2bCVE
Please notice that I didn't test it yet.
Will build such Kernel and see how it behaves with compat32.
If it works fine, I'll submit for stable.
Regards,
Mauro
next prev parent reply other threads:[~2018-03-27 11:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180325090010epcas1p2864bb6fe3cbc420bc71eb0e7f1c847f1@epcas1p2.samsung.com>
2018-03-25 8:59 ` Linux 3.18.102 Greg KH
2018-03-25 8:59 ` Greg KH
2018-03-25 9:51 ` Harsh Shandilya
2018-03-27 1:40 ` Seung-Woo Kim
2018-03-27 7:05 ` Greg KH
2018-03-27 7:31 ` Seung-Woo Kim
2018-03-27 7:53 ` Greg KH
2018-03-27 11:30 ` Mauro Carvalho Chehab [this message]
2018-03-28 16:27 ` CVE-2017-13166 fixes for Kernel 3.18 - was: " Mauro Carvalho Chehab
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=20180327083054.1d9b7796@vento.lan \
--to=mchehab@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=inki.dae@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sw0312.kim@samsung.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