<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - userptr deadlock in Vulkan CTS: mmu_notifier vs workers vs struct_mutex" href="https://bugs.freedesktop.org/show_bug.cgi?id=108456#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - userptr deadlock in Vulkan CTS: mmu_notifier vs workers vs struct_mutex" href="https://bugs.freedesktop.org/show_bug.cgi?id=108456">bug 108456</a> from <a class="email" href="mailto:tvrtko.ursulin@linux.intel.com" title="Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>"> Tvrtko Ursulin</a> <pre>CI_DRM_5255 or newer runs contain the fix. You look for the "success" in the summary block in the results email, but it is not 100% accurate. There are false positives, and of course false negatives as well, for all the issues which have no sufficient test coverage. The one my fix handles is unfortunately one of those - which answers the second part of your question. So you won't see the fail -> pass transition reliably before and after this fix. It does include new tests so from this point onward it will be caught. Note that this is not fixing the userptr problem, just the system hang after GPU hang which should enable more comfortable testing of Chris' proposed userptr fixes.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>