From: Greg KH <gregkh@linuxfoundation.org>
To: sikkamukul <mukul.sikka@broadcom.com>
Cc: stable@vger.kernel.org, evan.quan@amd.com,
alexander.deucher@amd.com, christian.koenig@amd.com,
airlied@linux.ie, daniel@ffwll.ch, Jun.Ma2@amd.com,
kevinyang.wang@amd.com, sashal@kernel.org,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, ajay.kaher@broadcom.com,
alexey.makhalov@broadcom.com, vasavi.sirnapalli@broadcom.com,
Bob Zhou <bob.zhou@amd.com>, Tim Huang <Tim.Huang@amd.com>
Subject: Re: [PATCH v5.15-v5.10] drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr
Date: Thu, 5 Sep 2024 09:40:30 +0200 [thread overview]
Message-ID: <2024090523-collide-colonize-d914@gregkh> (raw)
In-Reply-To: <20240903045809.5025-1-mukul.sikka@broadcom.com>
On Tue, Sep 03, 2024 at 04:58:09AM +0000, sikkamukul wrote:
> From: Bob Zhou <bob.zhou@amd.com>
>
> [ Upstream commit 50151b7f1c79a09117837eb95b76c2de76841dab ]
>
> Check return value and conduct null pointer handling to avoid null pointer dereference.
>
> Signed-off-by: Bob Zhou <bob.zhou@amd.com>
> Reviewed-by: Tim Huang <Tim.Huang@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> Signed-off-by: Mukul Sikka <mukul.sikka@broadcom.com>
> ---
> .../drm/amd/pm/powerplay/hwmgr/vega10_hwmgr.c | 30 ++++++++++++++++---
> 1 file changed, 26 insertions(+), 4 deletions(-)
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2024-09-05 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 4:58 [PATCH v5.15-v5.10] drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr sikkamukul
2024-09-05 7:40 ` Greg KH [this message]
2024-09-05 18:35 ` Alex Deucher
2024-09-06 8:50 ` Mukul Sikka
2024-09-06 15:02 ` Alex Deucher
2024-09-08 12:59 ` Greg KH
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=2024090523-collide-colonize-d914@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Jun.Ma2@amd.com \
--cc=Tim.Huang@amd.com \
--cc=airlied@linux.ie \
--cc=ajay.kaher@broadcom.com \
--cc=alexander.deucher@amd.com \
--cc=alexey.makhalov@broadcom.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bob.zhou@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=evan.quan@amd.com \
--cc=kevinyang.wang@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mukul.sikka@broadcom.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vasavi.sirnapalli@broadcom.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