From: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@linux.ie,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, gregkh@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
emil.l.velikov@gmail.com
Subject: Re: [PATCH v2 1/2] drm: Add a locked version of drm_is_current_master
Date: Fri, 18 Jun 2021 10:54:58 +0800 [thread overview]
Message-ID: <793cf08c-a766-637e-b473-91f6c8de12ec@gmail.com> (raw)
In-Reply-To: <YMuAYaZF+qW7GUFT@phenom.ffwll.local>
On 18/6/21 1:03 am, Daniel Vetter wrote:
> On Tue, Jun 15, 2021 at 10:36:44AM +0800, Desmond Cheong Zhi Xi wrote:
>> While checking the master status of the DRM file in
>> drm_is_current_master(), the device's master mutex should be
>> held. Without the mutex, the pointer fpriv->master may be freed
>> concurrently by another process calling drm_setmaster_ioctl(). This
>> could lead to use-after-free errors when the pointer is subsequently
>> dereferenced in drm_lease_owner().
>>
>> The callers of drm_is_current_master() from drm_auth.c hold the
>> device's master mutex, but external callers do not. Hence, we implement
>> drm_is_current_master_locked() to be used within drm_auth.c, and
>> modify drm_is_current_master() to grab the device's master mutex
>> before checking the master status.
>>
>> Reported-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>> Signed-off-by: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
>> Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
>> ---
>> drivers/gpu/drm/drm_auth.c | 23 +++++++++++++++++++----
>> 1 file changed, 19 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_auth.c b/drivers/gpu/drm/drm_auth.c
>> index 232abbba3686..c6bf52c310a9 100644
>> --- a/drivers/gpu/drm/drm_auth.c
>> +++ b/drivers/gpu/drm/drm_auth.c
>> @@ -61,6 +61,8 @@
>> * trusted clients.
>> */
>>
>> +static bool drm_is_current_master_locked(struct drm_file *fpriv);
>
> A bit a bikeshed, but we try to avoid forward declarations when they're
> not needed. If you don't want to tear apart drm_is_current_master and the
> _locked version then just move them together.
>
> Can you pls do that and respin?
>
> Otherwise looks all great.
> -Daniel
>
>
Yeah, I was trying to keep the logic in _locked close to
drm_is_current_master. But got it, will do.
next prev parent reply other threads:[~2021-06-18 2:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 2:36 [PATCH v2 0/2] drm: Address potential UAF bugs with drm_master ptrs Desmond Cheong Zhi Xi
2021-06-15 2:36 ` [PATCH v2 1/2] drm: Add a locked version of drm_is_current_master Desmond Cheong Zhi Xi
2021-06-17 17:03 ` Daniel Vetter
2021-06-18 2:54 ` Desmond Cheong Zhi Xi [this message]
2021-06-15 2:36 ` [PATCH v2 2/2] drm: Protect drm_master pointers in drm_lease.c Desmond Cheong Zhi Xi
2021-06-17 17:12 ` Daniel Vetter
2021-06-18 3:05 ` Desmond Cheong Zhi Xi
2021-06-18 9:12 ` Daniel Vetter
2021-06-18 16:54 ` Desmond Cheong Zhi Xi
2021-06-18 21:49 ` Daniel Vetter
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=793cf08c-a766-637e-b473-91f6c8de12ec@gmail.com \
--to=desmondcheongzx@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tzimmermann@suse.de \
/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