diff options
| author | Daniel Vetter <[email protected]> | 2024-07-10 11:31:16 +0200 |
|---|---|---|
| committer | Daniel Vetter <[email protected]> | 2024-07-18 15:39:54 +0200 |
| commit | 99e0fb8b087120b5a7019f1cff6c5c2b5b925ae5 (patch) | |
| tree | 2077ad54c9af61c514f318aad3f04b57a18ef597 /tools/perf/scripts/python/stackcollapse.py | |
| parent | ca5442ed8f5383f86bb9b4d66eeb816cd90aeb3b (diff) | |
drm: Add might_fault to drm_modeset_lock priming
We already teach lockdep that dma_resv nests within drm_modeset_lock,
but there's a lot more: All drm kms ioctl rely on being able to
put/get_user while holding modeset locks, so we really need a
might_fault in there too to complete the picture. Add it.
Motivated by a syzbot report that blew up on bcachefs doing an
unconditional console_lock way deep in the locking hierarchy, and
lockdep only noticing the depency loop in a drm ioctl instead of much
earlier. This annotation will make sure such issues have a much harder
time escaping.
References: https://lore.kernel.org/dri-devel/[email protected]/
Signed-off-by: Daniel Vetter <[email protected]>
Cc: Maarten Lankhorst <[email protected]>
Cc: Maxime Ripard <[email protected]>
Cc: Thomas Zimmermann <[email protected]>
Cc: Sumit Semwal <[email protected]>
Cc: "Christian König" <[email protected]>
Cc: [email protected]
Cc: [email protected]
Reviewed-by: Christian König <[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/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions