From: "Christian König" <christian.koenig@amd.com>
To: Philipp Stanner <phasta@kernel.org>,
Matthew Brost <matthew.brost@intel.com>,
Danilo Krummrich <dakr@kernel.org>,
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>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
James Flowers <bold.zone2373@fastmail.com>
Subject: Re: [PATCH v2] drm/sched: Document race condition in drm_sched_fini()
Date: Wed, 13 Aug 2025 11:03:09 +0200 [thread overview]
Message-ID: <36f76e46-580f-43d9-8726-fe13e0c1bba1@amd.com> (raw)
In-Reply-To: <20250813085654.102504-2-phasta@kernel.org>
On 13.08.25 10:56, Philipp Stanner wrote:
> In drm_sched_fini() all entities are marked as stopped - without taking
> the appropriate lock, because that would deadlock. That means that
> drm_sched_fini() and drm_sched_entity_push_job() can race against each
> other.
>
> This should most likely be fixed by establishing the rule that all
> entities associated with a scheduler must be torn down first. Then,
> however, the locking should be removed from drm_sched_fini() alltogether
> with an appropriate comment.
>
> Reported-by: James Flowers <bold.zone2373@fastmail.com>
> Link: https://lore.kernel.org/dri-devel/20250720235748.2798-1-bold.zone2373@fastmail.com/
> Signed-off-by: Philipp Stanner <phasta@kernel.org>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> Changes in v2:
> - Fix typo.
> ---
> drivers/gpu/drm/scheduler/sched_main.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/drivers/gpu/drm/scheduler/sched_main.c b/drivers/gpu/drm/scheduler/sched_main.c
> index 5a550fd76bf0..46119aacb809 100644
> --- a/drivers/gpu/drm/scheduler/sched_main.c
> +++ b/drivers/gpu/drm/scheduler/sched_main.c
> @@ -1424,6 +1424,22 @@ void drm_sched_fini(struct drm_gpu_scheduler *sched)
> * Prevents reinsertion and marks job_queue as idle,
> * it will be removed from the rq in drm_sched_entity_fini()
> * eventually
> + *
> + * FIXME:
> + * This lacks the proper spin_lock(&s_entity->lock) and
> + * is, therefore, a race condition. Most notably, it
> + * can race with drm_sched_entity_push_job(). The lock
> + * cannot be taken here, however, because this would
> + * lead to lock inversion -> deadlock.
> + *
> + * The best solution probably is to enforce the life
> + * time rule of all entities having to be torn down
> + * before their scheduler. Then, however, locking could
> + * be dropped alltogether from this function.
> + *
> + * For now, this remains a potential race in all
> + * drivers that keep entities alive for longer than
> + * the scheduler.
> */
> s_entity->stopped = true;
> spin_unlock(&rq->lock);
next prev parent reply other threads:[~2025-08-13 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 8:56 Philipp Stanner
2025-08-13 9:03 ` Christian König [this message]
2025-08-13 12:58 ` Danilo Krummrich
2025-08-28 8:28 ` Philipp Stanner
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=36f76e46-580f-43d9-8726-fe13e0c1bba1@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@gmail.com \
--cc=bold.zone2373@fastmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=phasta@kernel.org \
--cc=simona@ffwll.ch \
--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®