AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Antonio Quartulli <antonio@mandelbit.com>
Cc: amd-gfx@lists.freedesktop.org, alexander.deucher@amd.com,
	christian.koenig@amd.com, Xinhui.Pan@amd.com,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] amdgpu: prevent NULL pointer dereference if ATIF is not supported
Date: Thu, 31 Oct 2024 09:41:57 -0500	[thread overview]
Message-ID: <32298ecd-7b7c-4e19-8481-f35249d6e076@amd.com> (raw)
In-Reply-To: <77ba52f4-dcdc-4fdd-97b7-0163e54e8836@mandelbit.com>

On 10/30/2024 16:06, Antonio Quartulli wrote:
> Hi Mario,
> 
> On 30/10/2024 02:41, Mario Limonciello wrote:
>> On 10/29/2024 18:32, Antonio Quartulli wrote:
>>> acpi_evaluate_object() may return AE_NOT_FOUND (failure), which
>>> would result in dereferencing buffer.pointer (obj) while being NULL.
>>>
>>> Bail out also when status is AE_NOT_FOUND with a proper error message.
>>>
>>> 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>
>>
>> I'm not really sure how realistic this failure is.  Can you share the 
>> full call trace that Coverity identified?
> 
> I just checked Coverity Scan and it only says:
> 
>      5. Condition status, taking true branch.
>      6. Condition status != 5U /* (acpi_status)(5 | 0) */, taking false 
> branch.
> 
> The above points are related to:
> 
>      if (ACPI_FAILURE(status) && status != AE_NOT_FOUND)
> 
> It doesn't show how acpi_evaluate_object() is expected to return 
> AE_NOT_FOUND.
> 
> This said, if you think this case is unrealistic, why do you check for 
> "status != AE_NOT_FOUND" at all?
> 
> At this point maybe it would make more sense to simply drop this check 
> and always bail out with the current error message.
> 
> Basically a patch with the following only:
> 
> -       /* 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)) {
> 
> This way we don't make a fuzz for a possibly unrealistic case, while 
> still protecting against bugs and null-dereferences.

Yeah I think that's a good idea.  Can you respin it as a v2?

> 
> 
> Regards,
> 
>>
>> amdgpu_atif_pci_probe_handle() will check whether the handle is 
>> available in the first place.  We'll never this this far if that failed.
>>
>> Because of that I don't follow how this could return AE_NOT_FOUND.
>>> ---
>>>   drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c | 11 +++++++----
>>>   1 file changed, 7 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c b/drivers/gpu/ 
>>> drm/amd/amdgpu/amdgpu_acpi.c
>>> index cce85389427f..f10c3261a4ab 100644
>>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c
>>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c
>>> @@ -172,10 +172,13 @@ 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) {
>>> -        DRM_DEBUG_DRIVER("failed to evaluate ATIF got %s\n",
>>> -                 acpi_format_exception(status));
>>> +    /* Fail if calling the method fails */
>>> +    if (ACPI_FAILURE(status)) {
>>> +        if (status != AE_NOT_FOUND)
>>> +            DRM_DEBUG_DRIVER("failed to evaluate ATIF got %s\n",
>>> +                     acpi_format_exception(status));
>>> +        else
>>> +            DRM_DEBUG_DRIVER("ATIF not supported\n");
>>>           kfree(obj);
>>>           return NULL;
>>>       }
>>
> 


  reply	other threads:[~2024-10-31 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 23:32 [PATCH] amdgpu: prevent NULL pointer dereference if ATIF is not supported Antonio Quartulli
2024-10-30  1:41 ` Mario Limonciello
2024-10-30 21:06   ` Antonio Quartulli
2024-10-31 14:41     ` Mario Limonciello [this message]
2024-10-31 15:19       ` Antonio Quartulli

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=32298ecd-7b7c-4e19-8481-f35249d6e076@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox