| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |
Comment # 2
on bug 102650
from Chris Wilson
commit c7e116007e907f32c18cc2669e2dc4046553c8e6 (HEAD, upstream/master) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Sep 11 13:23:27 2017 +0100 igt/sw_sync: Fix up close(timeline) tests for unsignaled fences Following kernel commit ea4d5a270b57fa8d4871f372ca9b97b7697fdfda Author: Dominik Behr <dbehr@chromium.org> Date: Thu Sep 7 16:02:46 2017 -0300 dma-buf/sw_sync: force signal all unsignaled fences on dying timeline To avoid hanging userspace components that might have been waiting on the active fences of the destroyed timeline we need to signal with error all remaining fences on such timeline. This restore the default behaviour of the Android sw_sync framework, which Android still relies on. It was broken on the dma fence conversion a few years ago and never fixed. unsignaled fences are now signaled and flagged with ENOENT when the timeline is closed. Fixup timeline_closed_signaled to match. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=102650 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Michał Winiarski <michal.winiarski@intel.com>
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
