[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <061ca923-866d-2d31-8084-f4133e05b171@collabora.com>
Date: Mon, 14 Nov 2022 01:55:13 +0300
From: Dmitry Osipenko <dmitry.osipenko@...labora.com>
To: Dmitry Vyukov <dvyukov@...gle.com>,
Dave Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>,
DRI <dri-devel@...ts.freedesktop.org>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
LKML <linux-kernel@...r.kernel.org>,
Christian König <christian.koenig@....com>
Subject: Re: dealock in drm_fb_helper_damage_work
On 11/13/22 23:48, Dmitry Vyukov wrote:
>> Hi,
>>
>> I am getting the following deadlock on reservation_ww_class_mutex
>> while trying to boot next-20221111 kernel:
> The code is recently added by this commit:
>
> commit 79e2cf2e7a193473dfb0da3b9b869682b43dc60f
> Author: Dmitry Osipenko <dmitry.osipenko@...labora.com>
> Date: Mon Oct 17 20:22:11 2022 +0300
> drm/gem: Take reservation lock for vmap/vunmap operations
Thanks for the report. I reproduced this problem using bochs driver,
will send the fix ASAP.
--
Best regards,
Dmitry
Powered by blists - more mailing lists