From: "masashi.kudo@cybertrust.co.jp" <masashi.kudo@cybertrust.co.jp>
To: <cip-dev@lists.cip-project.org>, <cip-members@lists.cip-project.org>
Subject: [cip-dev] hitachi_omap defconfigs
Date: Wed, 16 Dec 2020 06:10:12 +0000 [thread overview]
Message-ID: <TY2PR01MB497230D728C09766E2AEDF8AA0C50@TY2PR01MB4972.jpnprd01.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
Hi, Hitachi-team,
Last week, CVE-2020-27820 [drm/nouveau UAF] was reported by the following email.
https://lore.kernel.org/cip-dev/CAGb2v641=SrfdDh9CS4fwWVrfuCG2O2oni9V_QsVJEza+g5mRg@mail.gmail.com/T/#u
According to the kernel team analysis, it seems that the nouveau driver is enabled in hitachi_omap defconfigs for both 4.4 and 4.19.
However, the configs are for OMAP platforms which, according to our understanding, don't have PCI for a graphics card.
So we think that the hitachi_omap defconfigs should be corrected to disable the nouveau driver.
We could be wrong, so please advise us. Once you confirm it to be corrected, we will go ahead to change it.
Best regards,
--
M. Kudo
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5966): https://lists.cip-project.org/g/cip-dev/message/5966
Mute This Topic: https://lists.cip-project.org/mt/78995356/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2020-12-16 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 6:10 masashi.kudo [this message]
2020-12-21 2:38 ` [cip-dev] hitachi_omap defconfigs Hidehiro Kawai
[not found] ` <16529B035A24E529.13568@lists.cip-project.org>
2020-12-25 6:33 ` Hidehiro Kawai
2020-12-25 9:27 ` masashi.kudo
2021-02-25 7:59 ` masashi.kudo
2021-02-26 12:40 ` Hidehiro Kawai
2021-02-27 9:27 ` masashi.kudo
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=TY2PR01MB497230D728C09766E2AEDF8AA0C50@TY2PR01MB4972.jpnprd01.prod.outlook.com \
--to=masashi.kudo@cybertrust.co.jp \
--cc=cip-dev@lists.cip-project.org \
--cc=cip-members@lists.cip-project.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 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).