<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - glClientWaitSync(..., GL_TIMEOUT_IGNORED) fails to wait for sync." href="https://bugs.freedesktop.org/show_bug.cgi?id=88344#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - glClientWaitSync(..., GL_TIMEOUT_IGNORED) fails to wait for sync." href="https://bugs.freedesktop.org/show_bug.cgi?id=88344">bug 88344</a> from <a class="email" href="mailto:lemody@gmail.com" title="Tapani Pälli <lemody@gmail.com>"> Tapani Pälli</a> <pre>please try again, should have been fixed by: ----------------------------------------------- commit 10c82c6c5fc415d323a5e9c6acdc6a4c85d6b712 Author: Kristian Høgsberg <<a href="mailto:krh@bitplanet.net">krh@bitplanet.net</a>> Date: Mon Mar 2 16:19:52 2015 -0800 i965: Fix uint64_t overflow in intel_client_wait_sync() DRM_IOCTL_I915_GEM_WAIT takes an int64_t for the timeout value but GL_ARB_sync takes an uint64_t. Further, the ioctl used to wait indefinitely when passed a negative timeout, but it's been broken and now returns immediately in that case. Thus, if an application passes UINT64_MAX to wait forever, we overflow to -1LL and return immediately. Work around this mess by clamping the wait timeout to INT64_MAX. Signed-off-by: Kristian Høgsberg <<a href="mailto:krh@bitplanet.net">krh@bitplanet.net</a>> Reviewed-by: Chad Versace <<a href="mailto:chad.versace@intel.com">chad.versace@intel.com</a>></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>