Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: 4.19+
The bot has tested the following trees: v5.6.5, v5.5.18, v5.4.33, v4.19.116.
v5.6.5: Build OK!
v5.5.18: Build OK!
v5.4.33: Build OK!
v4.19.116: Failed to apply! Possible dependencies:
57a3a454f303 ("iwlwifi: split HE capabilities between AP and STA")
80aaa9c16415 ("mac80211: Add he_capa debugfs entry")
add7453ad62f ("wireless: align to draft 11ax D3.0")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
From: Sultan Alsawaf <sultan(a)kerneltoast.com>
Hi,
There's a mutex lock deadlock in i915 that only affects 5.4, but was fixed in
5.5. Normally, I would send a backport of the fix from 5.5, but the patch set
that fixes the deadlock involves massive changes that are neither feasible nor
desirable for backporting [1][2][3]. Therefore, I've made a small patch that
only addresses the deadlock specifically for 5.4.
Thanks,
Sultan
[1] 274cbf20fd10 ("drm/i915: Push the i915_active.retire into a worker")
[2] 093b92287363 ("drm/i915: Split i915_active.mutex into an irq-safe spinlock for the rbtree")
[3] 750bde2fd4ff ("drm/i915: Serialise with remote retirement")
Sultan Alsawaf (1):
drm/i915: Fix ref->mutex deadlock in i915_active_wait()
drivers/gpu/drm/i915/i915_active.c | 27 +++++++++++++++++++++++----
drivers/gpu/drm/i915/i915_active.h | 4 ++--
2 files changed, 25 insertions(+), 6 deletions(-)
--
2.26.0