From: Greg KH <gregkh@linuxfoundation.org>
To: jianqi.ren.cn@windriver.com
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
alexander.deucher@amd.com, daniel.wheeler@amd.com,
mario.limonciello@amd.com, josip.pavic@amd.com,
aurabindo.pillai@amd.com, sohaib.nadeem@amd.com,
harry.wentland@amd.com, sunpeng.li@amd.com,
Rodrigo.Siqueira@amd.com, christian.koenig@amd.com,
Xinhui.Pan@amd.com, airlied@gmail.com, daniel@ffwll.ch,
wayne.lin@amd.com, sashal@kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
charlene.liu@amd.com, gabe.teeger@amd.com,
amd-gfx@lists.freedesktop.org, Nicholas.Kazlauskas@amd.com
Subject: Re: [PATCH 6.1.y] drm/amd/display: fixed integer types and null check locations
Date: Wed, 5 Mar 2025 13:59:28 +0100 [thread overview]
Message-ID: <2025030548-spinal-breezy-ef8e@gregkh> (raw)
In-Reply-To: <20250227032633.4176866-1-jianqi.ren.cn@windriver.com>
On Thu, Feb 27, 2025 at 11:26:33AM +0800, jianqi.ren.cn@windriver.com wrote:
> From: Sohaib Nadeem <sohaib.nadeem@amd.com>
>
> [ Upstream commit 0484e05d048b66d01d1f3c1d2306010bb57d8738 ]
>
> [why]:
> issues fixed:
> - comparison with wider integer type in loop condition which can cause
> infinite loops
> - pointer dereference before null check
>
> Cc: Mario Limonciello <mario.limonciello@amd.com>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Cc: stable@vger.kernel.org
> Reviewed-by: Josip Pavic <josip.pavic@amd.com>
> Acked-by: Aurabindo Pillai <aurabindo.pillai@amd.com>
> Signed-off-by: Sohaib Nadeem <sohaib.nadeem@amd.com>
> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> [ To fix CVE-2024-26767, delete changes made in drivers/gpu/drm/amd/display/dc/link/link_validation.c
> for this file is deleted in linux-6.1 ]
It's not that the file is deleted, it is just not present yet, as it had
not shown up in the tree.
I've manually edited this changelog, please be more careful next time.
Also, no need to mention a CVE id, they don't mean anything here :)
thanks,
greg k-h
next prev parent reply other threads:[~2025-03-05 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 3:26 [PATCH 6.1.y] drm/amd/display: fixed integer types and null check locations jianqi.ren.cn
2025-03-05 12:59 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-24 4:08 Imkanmod Khan
2024-12-11 10:07 jianqi.ren.cn
2024-12-09 6:50 jianqi.ren.cn
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=2025030548-spinal-breezy-ef8e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pillai@amd.com \
--cc=charlene.liu@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel.wheeler@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gabe.teeger@amd.com \
--cc=harry.wentland@amd.com \
--cc=jianqi.ren.cn@windriver.com \
--cc=josip.pavic@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=patches@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=sohaib.nadeem@amd.com \
--cc=stable@vger.kernel.org \
--cc=sunpeng.li@amd.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