<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90537#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90537">bug 90537</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to Christian König from <a href="show_bug.cgi?id=90537#c6">comment #6</a>)
<span class="quote">>
> But in your case it looks like that mesa drops the last reference and the
> buffer isn't freed. This means that somebody has still a reference to the
> buffer which is a bit odd.
>
> It probably points to a bug somewhere.</span >
Not necessarily if the BO is shared. E.g. in the Xorg radeon driver we have to
leak a reference to the fbcon BO because of this issue.
Another possibility is that the same BO is referenced by several GEM handles in
the same DRM fd, e.g. because it's re-imported via GEM flink. In that case, my
patch is probably the wrong solution, as it would make the BO unusable via the
other GEM handle.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>