diff options
author | Dave Airlie <airlied@redhat.com> | 2015-06-15 00:34:28 (GMT) |
---|---|---|
committer | Dave Airlie <airlied@redhat.com> | 2015-06-25 01:57:23 (GMT) |
commit | 6b8eeca65b18ae77e175cc2b6571731f0ee413bf (patch) | |
tree | df8de7144582b43d6e90024dc1a88fc873906499 /fs | |
parent | 8b72ce158cf0dba443e36fc66e0bb29c2580e0b6 (diff) | |
download | linux-6b8eeca65b18ae77e175cc2b6571731f0ee413bf.tar.xz |
drm/dp/mst: close deadlock in connector destruction.
I've only seen this once, and I failed to capture the
lockdep backtrace, but I did some investigations.
If we are calling into the MST layer from EDID probing,
we have the mode_config mutex held, if during that EDID
probing, the MST hub goes away, then we can get a deadlock
where the connector destruction function in the driver
tries to retake the mode config mutex.
This offloads connector destruction to a workqueue,
and avoid the subsequenct lock ordering issue.
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: stable@vger.kernel.org
Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions