From: Maciej Patelczyk <maciej.patelczyk@intel.com>
To: <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/gt: Ensure irqs' status does not change with spin_unlock
Date: Mon, 13 Jan 2025 10:36:54 +0100 [thread overview]
Message-ID: <5f339c78-c641-44ed-84c3-cc1972bc22dd@intel.com> (raw)
In-Reply-To: <gtrmxhovj2qpmcica76f7uxharhztbt7fdoromyxbsd7ltjvuq@lhnv2wcxm7or>
On 10.01.2025 15:08, Krzysztof Karas wrote:
> spin_unlock() function enables irqs regardless of their state
> before spin_lock() was called. This might result in an interrupt
> while holding a lock further down in the execution, as seen in
> GitLab issue #13399.
>
> Try to remedy the problem by saving irq state before spin lock
> acquisition.
>
> Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
> ---
> This issue is hit rarely on CI and I was not able to reproduce
> it locally. There might be more places where we should save and
> restore irq state, so I am not adding "Closes" label for the
> issue yet.
>
> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> index 12f1ba7ca9c1..e9102f7246f5 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> @@ -4338,10 +4338,11 @@ static void guc_bump_inflight_request_prio(struct i915_request *rq,
> static void guc_retire_inflight_request_prio(struct i915_request *rq)
> {
> struct intel_context *ce = request_to_scheduling_context(rq);
> + unsigned long flags;
>
> - spin_lock(&ce->guc_state.lock);
> + spin_lock_irqsave(&ce->guc_state.lock, flags);
> guc_prio_fini(rq, ce);
> - spin_unlock(&ce->guc_state.lock);
> + spin_unlock_irqrestore(&ce->guc_state.lock, flags);
> }
>
> static void sanitize_hwsp(struct intel_engine_cs *engine)
The guc_retire_inflight_request_prio is called in intel_breadcrumbs.c
signal_irq_work().
There is a similar situation
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/gt/intel_breadcrumbs.c?h=v6.13-rc7#n255
There is also spin_(un)lock while potentially IRQs are disabled.
Should it also be addressed?
Regards,
Maciej
next prev parent reply other threads:[~2025-01-13 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 14:08 [PATCH] drm/i915/gt: Ensure irqs' status does not change with spin_unlock Krzysztof Karas
2025-01-13 9:36 ` Maciej Patelczyk [this message]
2025-01-13 14:06 ` Krzysztof Karas
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=5f339c78-c641-44ed-84c3-cc1972bc22dd@intel.com \
--to=maciej.patelczyk@intel.com \
--cc=dri-devel@lists.freedesktop.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