mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Price <steven.price@arm.com>
To: Chia-I Wu <olvaffe@gmail.com>,
	Boris Brezillon <boris.brezillon@collabora.com>
Cc: Liviu Dudau <liviu.dudau@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>,
	Grant Likely <grant.likely@linaro.org>,
	Heiko Stuebner <heiko@sntech.de>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	tvrtko.ursulin@igalia.com
Subject: Re: [PATCH v2] drm/panthor: fix for dma-fence safe access rules
Date: Wed, 17 Dec 2025 15:55:42 +0000	[thread overview]
Message-ID: <42a3d2dc-1e1a-49ef-b3e7-c2fe604ca09a@arm.com> (raw)
In-Reply-To: <CAPaKu7RNOXSza-YP5cqnasPgs2E8HQ4yUzm4N2F649HgNxb18g@mail.gmail.com>

On 05/12/2025 18:45, Chia-I Wu wrote:
> On Fri, Dec 5, 2025 at 4:43 AM Boris Brezillon
> <boris.brezillon@collabora.com> wrote:
>>
>> On Thu,  4 Dec 2025 09:45:45 -0800
>> Chia-I Wu <olvaffe@gmail.com> wrote:
>>
>>> Commit 506aa8b02a8d6 ("dma-fence: Add safe access helpers and document
>>> the rules") details the dma-fence safe access rules. The most common
>>> culprit is that drm_sched_fence_get_timeline_name may race with
>>> group_free_queue.
>>>
>>> Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
>>> Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
>>> Reviewed-by: Liviu Dudau <liviu.dudau@arm.com>
>>> Reviewed-by: Steven Price <steven.price@arm.com>
>>>
>>> ---
>>> v2: collect R-bs and drop misleading Fixes: tag
>>
>> Should we at least
>>
>> Cc: stable@vger.kernel.org
>>
>> so this gets considered for backporting?
> This can be considered a follow-up to commit 506aa8b02a8d6. I think
> 
>   Cc: stable@vger.kernel.org # v6.17+
> 
> is appropriate. (Not sure if I should send v3 or leave it to
> maintainers, because I was once told to never add the line and always
> leave it to maintainers).
> 
> To help make the decision, commit 506aa8b02a8d6 itself narrowed the
> race window greatly. This follow-up closes the remaining case where
> panthor signals the fence and destroys the group while the consumer
> holds the rcu read lock.
> 

I've pushed this to drm-misc-next with the Cc tag.

Thanks,
Steve

>>
>>> ---
>>>  drivers/gpu/drm/panthor/panthor_sched.c | 4 ++++
>>>  1 file changed, 4 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/panthor/panthor_sched.c b/drivers/gpu/drm/panthor/panthor_sched.c
>>> index 33b9ef537e359..a8b1347e4da71 100644
>>> --- a/drivers/gpu/drm/panthor/panthor_sched.c
>>> +++ b/drivers/gpu/drm/panthor/panthor_sched.c
>>> @@ -23,6 +23,7 @@
>>>  #include <linux/module.h>
>>>  #include <linux/platform_device.h>
>>>  #include <linux/pm_runtime.h>
>>> +#include <linux/rcupdate.h>
>>>
>>>  #include "panthor_devfreq.h"
>>>  #include "panthor_device.h"
>>> @@ -923,6 +924,9 @@ static void group_release_work(struct work_struct *work)
>>>                                                  release_work);
>>>       u32 i;
>>>
>>> +     /* dma-fences may still be accessing group->queues under rcu lock. */
>>> +     synchronize_rcu();
>>> +
>>>       for (i = 0; i < group->queue_count; i++)
>>>               group_free_queue(group, group->queues[i]);
>>>
>>


      reply	other threads:[~2025-12-17 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 17:45 Chia-I Wu
2025-12-05 12:43 ` Boris Brezillon
2025-12-05 18:45   ` Chia-I Wu
2025-12-17 15:55     ` Steven Price [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=42a3d2dc-1e1a-49ef-b3e7-c2fe604ca09a@arm.com \
    --to=steven.price@arm.com \
    --cc=airlied@gmail.com \
    --cc=boris.brezillon@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=grant.likely@linaro.org \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=olvaffe@gmail.com \
    --cc=simona@ffwll.ch \
    --cc=tvrtko.ursulin@igalia.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®