From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Cc: "Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
linux-renesas-soc@vger.kernel.org,
"Hans Verkuil" <hverkuil@xs4all.nl>,
"Ramesh Shanmugasundaram"
<ramesh.shanmugasundaram@bp.renesas.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Jonathan Corbet" <corbet@lwn.net>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
"Kukjin Kim" <kgene@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 00/11] fix potential Spectre variant 1 issues
Date: Mon, 23 Apr 2018 14:13:58 -0500 [thread overview]
Message-ID: <96bd3e25-9503-d23d-4e3c-091e68b6bf8f@embeddedor.com> (raw)
In-Reply-To: <cover.1524499368.git.gustavo@embeddedor.com>
Hi,
Please, drop this series. Further analysis is required as it seems all
these are False Positives.
Sorry for the noise.
Thanks
--
Gustavo
On 04/23/2018 12:37 PM, Gustavo A. R. Silva wrote:
> This patchset aims to fix various media platform and media usb
> cases where we have user controlled array dereferences that could
> be exploited due to the Spectre variant 1 vulnerability. All were
> reported by Dan Carpenter.
>
> Notice that given that speculation windows are large, the policy is
> to kill the speculation on the first load and not worry if it can be
> completed with a dependent load/store [1].
>
> [1] https://marc.info/?l=linux-kernel&m=152449131114778&w=2
>
> Thanks
>
> Gustavo A. R. Silva (11):
> media: tm6000: fix potential Spectre variant 1
> exynos4-is: mipi-csis: fix potential Spectre variant 1
> fsl-viu: fix potential Spectre variant 1
> marvell-ccic: mcam-core: fix potential Spectre variant 1
> omap_vout: fix potential Spectre variant 1
> rcar-v4l2: fix potential Spectre variant 1
> rcar_drif: fix potential Spectre variant 1
> sh_vou: fix potential Spectre variant 1
> vimc-debayer: fix potential Spectre variant 1
> vivid-sdr-cap: fix potential Spectre variant 1
> vsp1_rwpf: fix potential Spectre variant 1
>
> drivers/media/platform/exynos4-is/mipi-csis.c | 5 ++++-
> drivers/media/platform/fsl-viu.c | 8 ++++----
> drivers/media/platform/marvell-ccic/mcam-core.c | 3 +++
> drivers/media/platform/omap/omap_vout.c | 3 +++
> drivers/media/platform/rcar-vin/rcar-v4l2.c | 4 +++-
> drivers/media/platform/rcar_drif.c | 4 +++-
> drivers/media/platform/sh_vou.c | 3 +++
> drivers/media/platform/vimc/vimc-debayer.c | 5 ++++-
> drivers/media/platform/vivid/vivid-sdr-cap.c | 6 ++++++
> drivers/media/platform/vsp1/vsp1_rwpf.c | 3 +++
> drivers/media/usb/tm6000/tm6000-video.c | 2 ++
> 11 files changed, 38 insertions(+), 8 deletions(-)
>
prev parent reply other threads:[~2018-04-23 19:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 17:37 [PATCH 00/11] fix potential Spectre variant 1 issues Gustavo A. R. Silva
2018-04-23 17:38 ` [PATCH 01/11] media: tm6000: fix potential Spectre variant 1 Gustavo A. R. Silva
2018-04-23 18:24 ` Mauro Carvalho Chehab
2018-04-23 19:11 ` Gustavo A. R. Silva
2018-04-23 19:17 ` Mauro Carvalho Chehab
2018-04-23 19:22 ` Gustavo A. R. Silva
2018-04-26 21:41 ` Gustavo A. R. Silva
2018-04-26 23:42 ` Mauro Carvalho Chehab
2018-05-15 3:31 ` Gustavo A. R. Silva
2018-05-15 11:59 ` Mauro Carvalho Chehab
2018-05-15 14:16 ` Dan Carpenter
2018-05-15 17:29 ` Gustavo A. R. Silva
2018-05-15 19:00 ` Mauro Carvalho Chehab
2018-05-16 13:11 ` Dan Carpenter
2018-05-16 13:36 ` Mauro Carvalho Chehab
2018-05-15 19:39 ` Dan Carpenter
2018-05-17 1:14 ` Gustavo A. R. Silva
2018-05-17 10:36 ` Gustavo A. R. Silva
2018-05-17 11:34 ` Mauro Carvalho Chehab
2018-05-17 11:43 ` Mauro Carvalho Chehab
2018-05-17 12:13 ` Mauro Carvalho Chehab
2018-05-17 18:08 ` Gustavo A. R. Silva
2018-05-21 16:18 ` Gustavo A. R. Silva
2018-04-24 9:35 ` Dan Carpenter
2018-04-24 10:11 ` Mauro Carvalho Chehab
2018-04-24 10:36 ` Peter Zijlstra
2018-04-24 11:21 ` Peter Zijlstra
2018-04-24 17:47 ` Mauro Carvalho Chehab
2018-04-24 18:48 ` Peter Zijlstra
2018-04-23 17:38 ` [PATCH 02/11] exynos4-is: mipi-csis: " Gustavo A. R. Silva
2018-04-23 17:39 ` [PATCH 03/11] fsl-viu: " Gustavo A. R. Silva
2018-04-23 17:40 ` [PATCH 04/11] marvell-ccic: mcam-core: " Gustavo A. R. Silva
2018-04-23 17:41 ` [PATCH 05/11] omap_vout: " Gustavo A. R. Silva
2018-04-23 17:47 ` [PATCH 06/11] rcar-v4l2: " Gustavo A. R. Silva
2018-04-23 17:48 ` [PATCH 07/11] rcar_drif: " Gustavo A. R. Silva
2018-04-23 17:48 ` [PATCH 08/11] sh_vou: " Gustavo A. R. Silva
2018-04-23 17:50 ` [PATCH 09/11] vimc-debayer: " Gustavo A. R. Silva
2018-04-23 17:51 ` [PATCH 10/11] vivid-sdr-cap: " Gustavo A. R. Silva
2018-04-23 17:52 ` [PATCH 11/11] vsp1_rwpf: " Gustavo A. R. Silva
2018-04-23 19:13 ` Gustavo A. R. Silva [this message]
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=96bd3e25-9503-d23d-4e3c-091e68b6bf8f@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=corbet@lwn.net \
--cc=dan.carpenter@oracle.com \
--cc=hverkuil@xs4all.nl \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=ramesh.shanmugasundaram@bp.renesas.com \
--cc=s.nawrocki@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;
as well as URLs for NNTP newsgroup(s).