From: Hans Verkuil <hverkuil@xs4all.nl>
To: Vladis Dronov <vdronov@redhat.com>,
Yuki Machida <machida.yuki@jp.fujitsu.com>
Cc: sasha levin <sasha.levin@oracle.com>,
linux-media@vger.kernel.org, stable@vger.kernel.org,
oneukum@suse.com, mchehab@osg.samsung.com, ralf@spenneberg.net
Subject: Re: Backport a Security Fix for CVE-2015-7833 to v4.1
Date: Fri, 15 Apr 2016 10:49:46 +0200 [thread overview]
Message-ID: <5710AB2A.50702@xs4all.nl> (raw)
In-Reply-To: <573811194.2583282.1460376200290.JavaMail.zimbra@redhat.com>
Hi Vladis,
On 04/11/2016 02:03 PM, Vladis Dronov wrote:
> Hello,
>
> I apologize for intercepting, but I believe commit 588afcc1 should
> not be accepted and reverted in the trees where it was.
Your patch requesting that commit to be reverted fell through the cracks.
Having looked at it I agree that it should be reverted and I will apply it.
The main reason is really the incorrect error return which should have been
a goto. But as you say reverting it is easiest since your code does the
right thing.
Regards,
Hans
>
> Reasons:
>
> https://patchwork.linuxtv.org/patch/32798/
> or
> https://www.spinics.net/lists/linux-media/msg96936.html
>
>
> Best regards,
> Vladis Dronov | Red Hat, Inc. | Product Security Engineer
>
> ----- Original Message -----
> From: "Yuki Machida" <machida.yuki@jp.fujitsu.com>
> To: "sasha levin" <sasha.levin@oracle.com>
> Cc: linux-media@vger.kernel.org, stable@vger.kernel.org, hverkuil@xs4all.nl, oneukum@suse.com, vdronov@redhat.com, mchehab@osg.samsung.com, ralf@spenneberg.net
> Sent: Monday, April 11, 2016 7:19:34 AM
> Subject: Backport a Security Fix for CVE-2015-7833 to v4.1
>
> Hi Sasha,
>
> I conformed that these patches for CVE-2015-7833 not applied at v4.1.21.
> 588afcc1c0e45358159090d95bf7b246fb67565
> fa52bd506f274b7619955917abfde355e3d19ff
> Could you please apply this CVE-2015-7833 fix for 4.1-stable ?
>
> References:
> https://security-tracker.debian.org/tracker/CVE-2015-7833
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=588afcc1c0e45358159090d95bf7b246fb67565f
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fa52bd506f274b7619955917abfde355e3d19ffe
>
> Regards,
> Yuki Machida
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-04-15 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 5:19 Backport a Security Fix for CVE-2015-7833 to v4.1 Yuki Machida
2016-04-11 12:03 ` Vladis Dronov
2016-04-15 8:31 ` Yuki Machida
2016-04-15 9:55 ` Vladis Dronov
2016-04-18 8:32 ` Yuki Machida
2016-04-18 9:20 ` Vladis Dronov
2016-04-19 8:17 ` Yuki Machida
2016-04-18 9:01 ` Yuki Machida
2016-04-19 5:55 ` Greg KH
2016-04-15 8:49 ` Hans Verkuil [this message]
2016-04-15 9:57 ` Vladis Dronov
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=5710AB2A.50702@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=machida.yuki@jp.fujitsu.com \
--cc=mchehab@osg.samsung.com \
--cc=oneukum@suse.com \
--cc=ralf@spenneberg.net \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=vdronov@redhat.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).