https://bugs.freedesktop.org/show_bug.cgi?id=98172
--- Comment #46 from Michel Dänzer <[email protected]> ---
(In reply to Suzuki, Shinji from comment #44)
> >=> r600_fence_reference and st_client_wait_sync continue working
> > with the fence object memory, which was already freed by thread
> > 1.
>
> I see that, since so->fence is duplicated at the beginning of the function,
> destruction of the fence object would never happen in the block covered by
> cmpxchg. If it ever happens then that would be by the 'unref' before the
> function exit.
Right, but there's nothing preventing that from happening before
r600_fence_reference in thread 0 calls pipe_reference. Mixing pipe_reference
and p_atomic_cmpxchg like this isn't safe.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
