From: Mihail Atanassov <mihail.atanassov@arm.com>
To: Liviu Dudau <liviu.dudau@arm.com>,
Boris Brezillon <boris.brezillon@collabora.com>
Cc: nd@arm.com, Steven Price <steven.price@arm.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Jann Horn <jannh@google.com>
Subject: Re: [PATCH] drm/panthor: Lock XArray when getting entries for heap and VM
Date: Wed, 6 Nov 2024 14:54:19 +0000 [thread overview]
Message-ID: <2f4a5d25-a804-4a3e-b4db-efce774b9692@arm.com> (raw)
In-Reply-To: <4e7bc9e6-f3d8-4e21-94d9-414ff0857553@arm.com>
On 06/11/2024 12:14, Mihail Atanassov wrote:
> Hi Liviu,
>
> On 06/11/2024 12:07, Liviu Dudau wrote:
>> Similar to cac075706f29 ("drm/panthor: Fix race when converting
>> group handle to group object") we need to use the XArray's internal
>> locking when retrieving a pointer from there for heap and vm.
>>
>> Reported-by: Jann Horn <jannh@google.com>
>> Cc: Boris Brezillon <boris.brezillon@collabora.com>
>> Cc: Steven Price <steven.price@arm.com>
>> Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
>> ---
>> drivers/gpu/drm/panthor/panthor_heap.c | 15 +++++++++++++--
>> drivers/gpu/drm/panthor/panthor_mmu.c | 2 ++
>> 2 files changed, 15 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/panthor/panthor_heap.c b/drivers/gpu/drm/
>> panthor/panthor_heap.c
>> index 3796a9eb22af2..fe0bcb6837f74 100644
>> --- a/drivers/gpu/drm/panthor/panthor_heap.c
>> +++ b/drivers/gpu/drm/panthor/panthor_heap.c
>> @@ -351,6 +351,17 @@ int panthor_heap_create(struct panthor_heap_pool
>> *pool,
>> return ret;
>> }
>> +static struct panthor_heap *panthor_heap_from_id(struct
>> pathor_heap_pool *pool, u32 id)
s/pathor/panthor/, but you already know that.
>> +{
>> + struct panthor_heap *heap;
>> +
>> + xa_lock(&pool->xa);
>> + heap = xa_load(&pool->xa, id);
>> + xa_unlock(&pool->va);
s/va/xa
>> +
>> + return heap;
>> +}
>> +
>> /**
>> * panthor_heap_return_chunk() - Return an unused heap chunk
>> * @pool: The pool this heap belongs to.
>> @@ -375,7 +386,7 @@ int panthor_heap_return_chunk(struct
>> panthor_heap_pool *pool,
>> return -EINVAL;
>> down_read(&pool->lock);
>> - heap = xa_load(&pool->xa, heap_id);
>> + heap = panthor_heap_from_id(pool, heap_id);
>> if (!heap) {
>> ret = -EINVAL;
>> goto out_unlock;
>> @@ -438,7 +449,7 @@ int panthor_heap_grow(struct panthor_heap_pool *pool,
>> return -EINVAL;
>> down_read(&pool->lock);
>> - heap = xa_load(&pool->xa, heap_id);
>> + heap = panthor_heap_from_id(pool, heap_id);
>> if (!heap) {
>> ret = -EINVAL;
>> goto out_unlock;
>> diff --git a/drivers/gpu/drm/panthor/panthor_mmu.c b/drivers/gpu/drm/
>> panthor/panthor_mmu.c
>> index 8ca85526491e6..8b5cda9d21768 100644
>> --- a/drivers/gpu/drm/panthor/panthor_mmu.c
>> +++ b/drivers/gpu/drm/panthor/panthor_mmu.c
>> @@ -1580,7 +1580,9 @@ panthor_vm_pool_get_vm(struct panthor_vm_pool
>> *pool, u32 handle)
>> {
>> struct panthor_vm *vm;
>> + xa_lock(&pool->xa);
>> vm = panthor_vm_get(xa_load(&pool->xa, handle));
>> + xa_unlock(&pool->va);
s/va/xa/
>> return vm;
>> }
>
> Reviewed-by: Mihail Atanassov <mihail.atanassov@arm.com>
Lesson learned for me -- at least build-test what you review :).
With the typos fixed up so this patch builds, I can't observe the race
in `panthor_vm_pool_get_vm` any more.
The other comments on this patch notwithstanding,
Tested-by: Mihail Atanassov <mihail.atanassov@arm.com>
>
--
Mihail Atanassov <mihail.atanassov@arm.com>
next prev parent reply other threads:[~2024-11-06 14:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 12:07 Liviu Dudau
2024-11-06 12:14 ` Mihail Atanassov
2024-11-06 14:54 ` Mihail Atanassov [this message]
2024-11-06 12:16 ` Boris Brezillon
2024-11-06 13:10 ` Liviu Dudau
2024-11-06 13:21 ` Boris Brezillon
2024-11-06 18:59 ` Liviu Dudau
2024-11-06 12:17 ` Boris Brezillon
2024-11-06 13:17 ` Steven Price
2024-11-06 13:34 ` Boris Brezillon
2024-11-06 13:40 ` Steven Price
2024-11-06 17:32 ` kernel test robot
2024-11-06 17:53 ` kernel test robot
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=2f4a5d25-a804-4a3e-b4db-efce774b9692@arm.com \
--to=mihail.atanassov@arm.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nd@arm.com \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--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
all inboxes | Powered by JetHome®