<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] igt@prime_busy@hang-blt - incomplete - kernel BUG at drivers/dma-buf/dma-buf.c:99!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111612#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] igt@prime_busy@hang-blt - incomplete - kernel BUG at drivers/dma-buf/dma-buf.c:99!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111612">bug 111612</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>commit 9b495a5887994a6d74d5c261d012083a92b94738
Author: Maarten Lankhorst <<a href="mailto:maarten.lankhorst@canonical.com">maarten.lankhorst@canonical.com</a>>
Date: Tue Jul 1 12:57:43 2014 +0200
dma-buf: add poll support, v3
...
@@ -52,6 +53,16 @@ static int dma_buf_release(struct inode *inode, struct file
*
file)
BUG_ON(dmabuf->vmapping_counter);
+ /*
+ * Any fences that a dma-buf poll can wait on should be signaled
+ * before releasing dma-buf. This is the responsibility of each
+ * driver that uses the reservation objects.
+ *
+ * If you hit this BUG() it means someone dropped their ref to the
+ * dma-buf while still having pending operation to the buffer.
+ */
+ BUG_ON(dmabuf->cb_shared.active || dmabuf->cb_excl.active);
which is quite odd as the exported dmabuf has no bearing on the native object
and its fences.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>