-------------------- Subject: [PATCH 2/6] Fix various layer context lock related deadlock scenarios
Changed dfb_layer_context_get_primary_region to return the error DFB_TEMPUNAVIL if the primary region is being destroyed. Previously in this scenario (which means the primary region's reference count was zero and there was not a request to create a new one), a deadlock could occur involving the layer context lock when the primary region was being destroyed by the main thread (single-app mode), the Fusion Loop thread (multi-app mode), or any other thread (such as linux_input thread that triggers the window stack input processing) is trying to get the primary region. In addition, object_reference_watcher would be called more than once when the reference count changes from 1 to 0 again in the implementation. -------------------- Cheers, Timothy -- Timothy Strelchun CE Software Engineering Digital Home Group Intel Corporation
0002-Fix-various-layer-context-lock-related-deadlock-scen.patch
Description: 0002-Fix-various-layer-context-lock-related-deadlock-scen.patch
_______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
