diff options
| author | Daniel Vetter <[email protected]> | 2017-12-04 21:48:18 +0100 |
|---|---|---|
| committer | Daniel Vetter <[email protected]> | 2017-12-06 10:22:55 +0100 |
| commit | a703c55004e1c5076d57e43771b3e11117796ea0 (patch) | |
| tree | 2be0916f74fc5e69786a4347e19f0d793cbf4309 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | ae64f9bd1d3621b5e60d7363bc20afb46aede215 (diff) | |
drm: safely free connectors from connector_iter
In
commit 613051dac40da1751ab269572766d3348d45a197
Author: Daniel Vetter <[email protected]>
Date: Wed Dec 14 00:08:06 2016 +0100
drm: locking&new iterators for connector_list
we've went to extreme lengths to make sure connector iterations works
in any context, without introducing any additional locking context.
This worked, except for a small fumble in the implementation:
When we actually race with a concurrent connector unplug event, and
our temporary connector reference turns out to be the final one, then
everything breaks: We call the connector release function from
whatever context we happen to be in, which can be an irq/atomic
context. And connector freeing grabs all kinds of locks and stuff.
Fix this by creating a specially safe put function for connetor_iter,
which (in this rare case) punts the cleanup to a worker.
Reported-by: Ben Widawsky <[email protected]>
Cc: Ben Widawsky <[email protected]>
Fixes: 613051dac40d ("drm: locking&new iterators for connector_list")
Cc: Dave Airlie <[email protected]>
Cc: Chris Wilson <[email protected]>
Cc: Sean Paul <[email protected]>
Cc: <[email protected]> # v4.11+
Reviewed-by: Dave Airlie <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions