From: "Hidehiro Kawai" <hidehiro.kawai.ez@hitachi.com>
To: "'masashi.kudo@cybertrust.co.jp'" <masashi.kudo@cybertrust.co.jp>,
"'wens@csie.org'" <wens@csie.org>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"cip-members@lists.cip-project.org"
<cip-members@lists.cip-project.org>
Subject: Re: [cip-dev] hitachi_omap defconfigs
Date: Fri, 25 Dec 2020 06:33:55 +0000 [thread overview]
Message-ID: <TYAPR01MB242955EF692D73FD473196EDB5DC0@TYAPR01MB2429.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <16529B035A24E529.13568@lists.cip-project.org>
[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]
Kudo-san and ChenYu-san,
We are sorry for the inconvenience. The confirmation will take some time.
If you'd like to solve this issue quickly, please disable nouveau driver now.
After the confirmation, we'll send an updated defconfig.
Best regards,
Hidehiro Kawai
Hitachi, Ltd. Research & Development Group
> From: cip-members@lists.cip-project.org <cip-members@lists.cip-project.org> On Behalf Of Hidehiro Kawai
>
> Hello Kudo-san and ChenYu-san,
>
> Thanks for reporting the issue.
> Including nouveau driver, it seems that our defconfigs have some unneeded drivers. I'm confirming this with our development
> team, please wait a moment.
>
> Best regards,
>
> Hidehiro Kawai
> Hitachi, Ltd. Research & Development Group
>
> > From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> > Behalf Of masashi.kudo@cybertrust.co.jp Hi, Hitachi-team,
> >
> > Last week, CVE-2020-27820 [drm/nouveau UAF] was reported by the following email.
> > https://clicktime.symantec.com/3Hrgtrrm6ninbLpVgrZpbS37Vc?u=https%3A%2
> > F%2Flore.kernel.org%2Fcip-dev%2FCAGb2v641%3DSr
> > fdDh9CS4fwWVrfuCG2O2oni9V_QsVJEza%2Bg5mRg%40mail.gmail.com%2FT%2F%23u
> >
> > 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 (#5976): https://lists.cip-project.org/g/cip-dev/message/5976
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 prev parent reply other threads:[~2020-12-25 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 6:10 [cip-dev] hitachi_omap defconfigs masashi.kudo
2020-12-21 2:38 ` Hidehiro Kawai
[not found] ` <16529B035A24E529.13568@lists.cip-project.org>
2020-12-25 6:33 ` Hidehiro Kawai [this message]
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=TYAPR01MB242955EF692D73FD473196EDB5DC0@TYAPR01MB2429.jpnprd01.prod.outlook.com \
--to=hidehiro.kawai.ez@hitachi.com \
--cc=cip-dev@lists.cip-project.org \
--cc=cip-members@lists.cip-project.org \
--cc=masashi.kudo@cybertrust.co.jp \
--cc=wens@csie.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).