From: Matt Coster <matt.coster@imgtec.com>
To: Frank Binns <frank.binns@imgtec.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>,
Brendan King <Brendan.King@imgtec.com>
Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>, Brendan King <brendan.king@imgtec.com>
Subject: Re: [PATCH v2] drm/imagination: avoid deadlock on fence release
Date: Mon, 3 Mar 2025 12:14:27 +0000 [thread overview]
Message-ID: <174100406750.47174.5779964447854559103.b4-ty@imgtec.com> (raw)
In-Reply-To: <20250226-fence-release-deadlock-v2-1-6fed2fc1fe88@imgtec.com>
On Wed, 26 Feb 2025 15:42:19 +0000, Brendan King wrote:
> Do scheduler queue fence release processing on a workqueue, rather
> than in the release function itself.
>
> Fixes deadlock issues such as the following:
>
> [ 607.400437] ============================================
> [ 607.405755] WARNING: possible recursive locking detected
> [ 607.415500] --------------------------------------------
> [ 607.420817] weston:zfq0/24149 is trying to acquire lock:
> [ 607.426131] ffff000017d041a0 (reservation_ww_class_mutex){+.+.}-{3:3}, at: pvr_gem_object_vunmap+0x40/0xc0 [powervr]
> [ 607.436728]
> but task is already holding lock:
> [ 607.442554] ffff000017d105a0 (reservation_ww_class_mutex){+.+.}-{3:3}, at: dma_buf_ioctl+0x250/0x554
> [ 607.451727]
> other info that might help us debug this:
> [ 607.458245] Possible unsafe locking scenario:
>
> [...]
Applied, thanks!
[1/1] drm/imagination: avoid deadlock on fence release
commit: df1a1ed5e1bdd9cc13148e0e5549f5ebcf76cf13
Best regards,
--
Matt Coster <matt.coster@imgtec.com>
prev parent reply other threads:[~2025-03-03 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 15:42 Brendan King via B4 Relay
2025-03-03 12:14 ` Matt Coster [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=174100406750.47174.5779964447854559103.b4-ty@imgtec.com \
--to=matt.coster@imgtec.com \
--cc=Brendan.King@imgtec.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank.binns@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--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®