Summary: | [ivb] mutex deadlock | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Chris Wilson <chris> | ||||||
Component: | DRM/Intel | Assignee: | Tvrtko Ursulin <tvrtko.ursulin> | ||||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Severity: | blocker | ||||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||||
Version: | DRI git | ||||||||
Hardware: | Other | ||||||||
OS: | All | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Chris Wilson
2015-02-16 13:30:21 UTC
Created attachment 113531 [details] [review] Eugh, this is ugly. Regression from commit ab8d66752a9c28cd6c94fa173feacdfc1554aa03 Author: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Date: Mon Feb 2 15:44:15 2015 +0000 drm/i915: Track old framebuffer instead of object update_state_fb() still holds the struct_mutex in almost all instances and looks pretty hard to extract. The other culprit is commit 60a5ca015ffd2aacfe5674b5a401cd2a37159e07 Author: Ville Syrjälä <ville.syrjala@linux.intel.com> Date: Fri Jun 13 11:10:53 2014 +0300 drm/i915: Add locking around framebuffer_references-- Created attachment 113537 [details] [review] Still ugly Could simply revert the culprit? It looked like it would be needed but the direction has changes since then so I am pretty sure it wouldn't affect anything. commit e0d6149b3debce1a7e17dfda7c2829935917dc58 Author: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Date: Mon Apr 13 16:03:03 2015 +0100 drm/i915: Move drm_framebuffer_unreference out of struct_mutex for takeover |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.