Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Krzysztof Karas <krzysztof.karas@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Maciej Patelczyk <maciej.patelczyk@intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	John Harrison <John.C.Harrison@intel.com>,
	Alan Previn <alan.previn.teres.alexis@intel.com>
Subject: Re: [PATCH v3] drm/i915/gt: Use spin_lock_irqsave() in interruptible context
Date: Thu, 13 Feb 2025 19:56:16 +0100	[thread overview]
Message-ID: <Z65AUD8Z6cfteuLd@ashyti-mobl2.lan> (raw)
In-Reply-To: <pusppq5ybyszau2oocboj3mtj5x574gwij323jlclm5zxvimmu@mnfg6odxbpsv>

Hi Krzysztof,

On Thu, Jan 16, 2025 at 10:40:46AM +0000, Krzysztof Karas wrote:
> spin_lock/unlock() functions used in interrupt contexts could
> result in a deadlock, as seen in GitLab issue #13399:
> https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13399,

I moved this link in the tag sectoin as Closes:

> which occurs when interrupt comes in while holding a lock.
> 
> Try to remedy the problem by saving irq state before spin lock
> acquisition.
> 
> v2: add irqs' state save/restore calls to all locks/unlocks in
>  signal_irq_work() execution (Maciej)
> 
> v3: use with spin_lock_irqsave() in guc_lrc_desc_unpin() instead
>  of other lock/unlock calls and add Fixes and Cc tags (Tvrtko);
>  change title and commit message
> 
> Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
> Fixes: 2f2cc53b5fe7 ("drm/i915/guc: Close deregister-context race against CT-loss")

I moved Fixes: above your SoB.

> Cc: <stable@vger.kernel.org> # v6.9+

Anyway, good catch, but please, remember next time to relly add
in Cc the stable kernel mailing list, the guc guys in Cc for GuC
related patches and the author of the patch you are fixing.

Reviewed and merged in drm-intel-gt-next.

Thanks,
Andi

      parent reply	other threads:[~2025-02-13 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 10:40 [PATCH v3] drm/i915/gt: Use spin_lock_irqsave() in interruptible context Krzysztof Karas
2025-01-16 11:22 ` Maciej Patelczyk
2025-01-16 12:13 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2025-01-16 13:18 ` ✗ i915.CI.BAT: failure " Patchwork
2025-01-17 11:51   ` Krzysztof Karas
2025-01-20  9:25     ` Ravali, JupallyX
2025-01-20  9:20 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-21  4:20 ` ✗ i915.CI.Full: failure " Patchwork
2025-01-31 10:40 ` ✓ i915.CI.BAT: success for drm/i915/gt: Use spin_lock_irqsave() in interruptible context (rev2) Patchwork
2025-01-31 12:52 ` ✓ i915.CI.Full: " Patchwork
2025-02-13 18:56 ` Andi Shyti [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=Z65AUD8Z6cfteuLd@ashyti-mobl2.lan \
    --to=andi.shyti@linux.intel.com \
    --cc=John.C.Harrison@intel.com \
    --cc=alan.previn.teres.alexis@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=krzysztof.karas@intel.com \
    --cc=maciej.patelczyk@intel.com \
    --cc=tursulin@ursulin.net \
    /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