Re: [PATCH hmm] drm/amdkfd: fix a use after free race with mmu_notififer unregister

2019-08-06 Thread Christoph Hellwig
Btw, who maintains amkfd these days? MAINTAINERS still lists Oded, but he seems to have moved on to Habanalabs and maintains that drivers now while not having any action on amdkfd for over a year. ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org ht

Re: [PATCH hmm] drm/amdkfd: fix a use after free race with mmu_notififer unregister

2019-08-06 Thread Oded Gabbay
On Tue, Aug 6, 2019 at 10:31 AM Christoph Hellwig wrote: > > Btw, who maintains amkfd these days? MAINTAINERS still lists > Oded, but he seems to have moved on to Habanalabs and maintains that > drivers now while not having any action on amdkfd for over a year. I've sent a patch to update the MA

Re: [PATCH hmm] drm/amdkfd: fix a use after free race with mmu_notififer unregister

2019-08-04 Thread Kuehling, Felix
On 2019-08-02 16:07, Jason Gunthorpe wrote: > When using mmu_notififer_unregister_no_release() the caller must ensure > there is a SRCU synchronize before the mn memory is freed, otherwise use > after free races are possible, for instance: > > CPU0 CPU1 >

[PATCH hmm] drm/amdkfd: fix a use after free race with mmu_notififer unregister

2019-08-02 Thread Jason Gunthorpe
When using mmu_notififer_unregister_no_release() the caller must ensure there is a SRCU synchronize before the mn memory is freed, otherwise use after free races are possible, for instance: CPU0 CPU1 invalidate_range_s