From: bodefang <bodefang@126.com>
To: "Alex Deucher" <alexdeucher@gmail.com>
Cc: Dave Airlie <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>,
"Deucher, Alexander" <alexander.deucher@amd.com>
Subject: Re:Re: [PATCH] drm/radeon:avoid null pointer dereference when dev is not bound
Date: Tue, 5 Jan 2021 10:43:41 +0800 (CST) [thread overview]
Message-ID: <42261169.1535.176d06dbef6.Coremail.bodefang@126.com> (raw)
In-Reply-To: <CADnq5_NhD5WUft5BnBrSjMn4x=5tb5Pje1_BUJyu60FtiFpNpw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1990 bytes --]
I use static analysis tool to find these funcs are similar to the commit<0fa375e6bc90>(drm/rockchip: Fix suspend crash when drm is not bound),so it's just defensive,
I haven't actually hitted this.
At 2021-01-05 01:00:27, "Alex Deucher" <alexdeucher@gmail.com> wrote:
>On Sun, Dec 27, 2020 at 3:56 PM Defang Bo <bodefang@126.com> wrote:
>>
>> [Why]
>> Similar to commit<0fa375e6>. If the set_state/can_switch code access the drm_device when dev is not bound,
>> a null pointer dereference can happen.
>>
>> [How]
>> Add sanity checks to prevent it.
>>
>> Signed-off-by: Defang Bo <bodefang@126.com>
>
>Are you actually hitting this or is this just defensive? I don't
>think we can actually get into a state where this would be a problem.
>
>Alex
>
>> ---
>> drivers/gpu/drm/radeon/radeon_device.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/radeon/radeon_device.c b/drivers/gpu/drm/radeon/radeon_device.c
>> index 266e3cb..50a1a60 100644
>> --- a/drivers/gpu/drm/radeon/radeon_device.c
>> +++ b/drivers/gpu/drm/radeon/radeon_device.c
>> @@ -1224,6 +1224,9 @@ static void radeon_switcheroo_set_state(struct pci_dev *pdev, enum vga_switchero
>> {
>> struct drm_device *dev = pci_get_drvdata(pdev);
>>
>> + if (!dev)
>> + return;
>> +
>> if (radeon_is_px(dev) && state == VGA_SWITCHEROO_OFF)
>> return;
>>
>> @@ -1257,6 +1260,9 @@ static void radeon_switcheroo_set_state(struct pci_dev *pdev, enum vga_switchero
>> static bool radeon_switcheroo_can_switch(struct pci_dev *pdev)
>> {
>> struct drm_device *dev = pci_get_drvdata(pdev);
>> +
>> + if (!dev)
>> + return false;
>>
>> /*
>> * FIXME: open_count is protected by drm_global_mutex but that would lead to
>> --
>> 2.7.4
>>
>> _______________________________________________
>> amd-gfx mailing list
>> amd-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
[-- Attachment #1.2: Type: text/html, Size: 2578 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2021-01-05 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 8:24 [PATCH] drm/radeon:avoid null pointer dereference when dev is not bound Defang Bo
2021-01-04 17:00 ` Alex Deucher
2021-01-05 2:43 ` bodefang [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=42261169.1535.176d06dbef6.Coremail.bodefang@126.com \
--to=bodefang@126.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--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