https://gitlab.freedesktop.org/mesa/mesa/merge_requests/605
Can you try that please and maybe discuss there as well? I cleaned up
the code a bit and realigned it with the radeon code.
Dave.
On Tue, 9 Apr 2019 at 04:44, Chia-I Wu wrote:
>
>
>
> On Mon, Apr 8, 2019 at 11:24 AM Lepton Wu wrote:
>
On Mon, Apr 8, 2019 at 11:24 AM Lepton Wu wrote:
> On Mon, Apr 8, 2019 at 11:10 AM Chia-I Wu wrote:
> >
> >
> >
> > On Mon, Apr 8, 2019 at 9:34 AM Lepton Wu wrote:
> >>
> >> The old code could use gem name as key when inserting it to bo_handles
> >> hash table while trying to remove it from has
On Mon, Apr 8, 2019 at 11:10 AM Chia-I Wu wrote:
>
>
>
> On Mon, Apr 8, 2019 at 9:34 AM Lepton Wu wrote:
>>
>> The old code could use gem name as key when inserting it to bo_handles
>> hash table while trying to remove it from hash table with bo_handle as
>> key in virgl_hw_res_destroy and then i
On Mon, Apr 8, 2019 at 9:34 AM Lepton Wu wrote:
> The old code could use gem name as key when inserting it to bo_handles
> hash table while trying to remove it from hash table with bo_handle as
> key in virgl_hw_res_destroy and then it fail to remove it from bo_handles
> hash table. This triggers
The old code could use gem name as key when inserting it to bo_handles
hash table while trying to remove it from hash table with bo_handle as
key in virgl_hw_res_destroy and then it fail to remove it from bo_handles
hash table. This triggers use after free. Also, we should insert resource
to bo_nam
