From: Greg KH <gregkh@linuxfoundation.org>
To: wangzhu <wangzhu9@huawei.com>
Cc: "harry.wentland@amd.com" <harry.wentland@amd.com>,
"sunpeng.li@amd.com" <sunpeng.li@amd.com>,
"alexander.deucher@amd.com" <alexander.deucher@amd.com>,
"christian.koenig@amd.com" <christian.koenig@amd.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"sanglipeng1@jd.com" <sanglipeng1@jd.com>,
"sashal@kernel.org" <sashal@kernel.org>,
"wayne.lin@amd.com" <wayne.lin@amd.com>,
"joshua@froggi.es" <joshua@froggi.es>,
"hongao@uniontech.com" <hongao@uniontech.com>,
"cssk@net-c.es" <cssk@net-c.es>,
"nicholas.kazlauskas@amd.com" <nicholas.kazlauskas@amd.com>,
"chiahsuan.chung@amd.com" <chiahsuan.chung@amd.com>,
"mwen@igalia.com" <mwen@igalia.com>,
"roman.li@amd.com" <roman.li@amd.com>,
"aurabindo.pillai@amd.com" <aurabindo.pillai@amd.com>,
"hansen.dsouza@amd.com" <hansen.dsouza@amd.com>,
"Rodrigo.Siqueira@amd.com" <Rodrigo.Siqueira@amd.com>,
"Konstantin Meskhidze (A)" <konstantin.meskhidze@huawei.com>,
"aric.cyr@amd.com" <aric.cyr@amd.com>,
"jaehyun.chung@amd.com" <jaehyun.chung@amd.com>,
"mario.limonciello@amd.com" <mario.limonciello@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 答复: [PATCH v5.10] drm/amd/display: Wake DMCUB before executing GPINT commands
Date: Thu, 18 Apr 2024 11:52:43 +0200 [thread overview]
Message-ID: <2024041852-surrogate-nimbly-0538@gregkh> (raw)
In-Reply-To: <a0b467dd1c074758aa89a18fa7a9c6ab@huawei.com>
On Thu, Apr 18, 2024 at 03:19:46AM +0000, wangzhu wrote:
> Hi Greg, thanks for your reply. Since there is no patch to fix CVE-2023-52624 in linux-5.10, there is a patch in the linux-6.7 branch to fix it, its commit is 2ef98c6d753a744e333b7e34b9cf687040fba57d ("drm/amd/display: Wake DMCUB before executing GPINT commands"). When we apply this patch to linux-5.10, there are lots of conflicts, and we found there are lots of dependent patches, we do not apply all these patches since some are not meant to fix the cve, so we just get part of them, and for each patch we just get the part which is helpful to fix.
Why do you think that specific CVE is relevent to the 5.10.y kernel?
And if so, what about the ones newer than that, as you know I can not
take patches only for older kernels, that would leave newer branches
vulnerable to the same bug.
So please submit fixes for all branches that you wish to see resolved at
the same time.
thanks,
greg k-h
prev parent reply other threads:[~2024-04-18 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 2:43 [PATCH v5.10] drm/amd/display: Wake DMCUB before executing GPINT commands Zhu Wang
2024-04-16 4:48 ` Greg KH
2024-04-18 3:19 ` 答复: " wangzhu
2024-04-18 9:52 ` Greg KH [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=2024041852-surrogate-nimbly-0538@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Rodrigo.Siqueira@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aric.cyr@amd.com \
--cc=aurabindo.pillai@amd.com \
--cc=chiahsuan.chung@amd.com \
--cc=christian.koenig@amd.com \
--cc=cssk@net-c.es \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hansen.dsouza@amd.com \
--cc=harry.wentland@amd.com \
--cc=hongao@uniontech.com \
--cc=jaehyun.chung@amd.com \
--cc=joshua@froggi.es \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mwen@igalia.com \
--cc=nicholas.kazlauskas@amd.com \
--cc=roman.li@amd.com \
--cc=sanglipeng1@jd.com \
--cc=sashal@kernel.org \
--cc=sunpeng.li@amd.com \
--cc=wangzhu9@huawei.com \
--cc=wayne.lin@amd.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