From: Mario Limonciello <mario.limonciello@amd.com>
To: Antonio Quartulli <antonio@mandelbit.com>
Cc: Xinhui.Pan@amd.com, alexander.deucher@amd.com,
christian.koenig@amd.com, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] amdgpu: prevent NULL pointer dereference if ATIF is not supported
Date: Fri, 1 Nov 2024 11:22:11 -0500 [thread overview]
Message-ID: <af5edb6c-3075-420e-b52f-05844c728180@amd.com> (raw)
In-Reply-To: <34c84c6a-9b0d-4d04-9ce3-edf1bb850b2c@mandelbit.com>
On 10/31/2024 15:50, Antonio Quartulli wrote:
> On 31/10/2024 20:37, Mario Limonciello wrote:
>> On 10/31/2024 10:28, Antonio Quartulli wrote:
>>> acpi_evaluate_object() may return AE_NOT_FOUND (failure), which
>>> would result in dereferencing buffer.pointer (obj) while being NULL.
>>>
>>> Although this case may be unrealistic for the current code, it is
>>> still better to protect against possible bugs.
>>>
>>> Bail out also when status is AE_NOT_FOUND.
>>>
>>> This fixes 1 FORWARD_NULL issue reported by Coverity
>>> Report: CID 1600951: Null pointer dereferences (FORWARD_NULL)
>>>
>>> Signed-off-by: Antonio Quartulli <antonio@mandelbit.com>
>>
>> Can you please dig up the right Fixes: tag?
>
> Fixes: c9b7c809b89f ("drm/amd: Guard against bad data for ATIF ACPI
> method")
>
> Your commit :)
>
> Should I send v3 with the Fixes tag in it?
Don't worry about it, I'll pick it up while we commit it.
Thanks!
>
> Interestingly, this pattern of checking for AE_NOT_FOUND is shared by
> other functions, however, they don't try to dereference the pointer to
> the buffer before the return statement (which caused the Coverity report).
> It's the caller that checks if the return value is NULL or not.
>
> For this function it was the same, until you added this extra check on
> obj->type, without checking if obj was NULL or not.
>
> If we want to keep the original pattern and continue checking for
> AE_NOT_FOUND, we could rather do:
>
> - if (obj->type != ACPI_TYPE_BUFFER) {
> + if (obj && obj->type != ACPI_TYPE_BUFFER) {
>
> But this feel more like "bike shed color picking" than anything else :)
> Anyway, up to you Mario, I am open to change the patch again if the
> latter pattern is more preferable.
>
> Regards,
>
>>
>> Besides that, LGTM.
>>
>> Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
>>
>>> ---
>>> drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c b/drivers/gpu/
>>> drm/amd/amdgpu/amdgpu_acpi.c
>>> index cce85389427f..b8d4e07d2043 100644
>>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c
>>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c
>>> @@ -172,8 +172,8 @@ static union acpi_object *amdgpu_atif_call(struct
>>> amdgpu_atif *atif,
>>> &buffer);
>>> obj = (union acpi_object *)buffer.pointer;
>>> - /* Fail if calling the method fails and ATIF is supported */
>>> - if (ACPI_FAILURE(status) && status != AE_NOT_FOUND) {
>>> + /* Fail if calling the method fails */
>>> + if (ACPI_FAILURE(status)) {
>>> DRM_DEBUG_DRIVER("failed to evaluate ATIF got %s\n",
>>> acpi_format_exception(status));
>>> kfree(obj);
>>
>
prev parent reply other threads:[~2024-11-01 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 15:28 [PATCH v2] amdgpu: prevent NULL pointer dereference if ATIF is not supported Antonio Quartulli
2024-10-31 15:48 ` Markus Elfring
2024-10-31 19:37 ` Mario Limonciello
2024-10-31 20:50 ` Antonio Quartulli
2024-11-01 16:22 ` Mario Limonciello [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=af5edb6c-3075-420e-b52f-05844c728180@amd.com \
--to=mario.limonciello@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=antonio@mandelbit.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.