Re: [PATCH] drm/msm: Ensure mmap offset is initialized

On Tue, 31 May 2022 at 23:37, Rob Clark wrote: > > On Tue, May 31, 2022 at 1:34 PM Dmitry Baryshkov > wrote: > > > > On Tue, 31 May 2022 at 23:08, Rob Clark wrote: > > > > > > From: Rob Clark > > > > > > If a GEM object is allocated, and then exported as a dma-buf fd which is > > > mmap'd

Re: [PATCH] drm/msm: Ensure mmap offset is initialized

On Tue, May 31, 2022 at 1:34 PM Dmitry Baryshkov wrote: > > On Tue, 31 May 2022 at 23:08, Rob Clark wrote: > > > > From: Rob Clark > > > > If a GEM object is allocated, and then exported as a dma-buf fd which is > > mmap'd before or without the GEM buffer being directly mmap'd, the > > vma_node

Re: [PATCH] drm/msm: Ensure mmap offset is initialized

On Tue, 31 May 2022 at 23:08, Rob Clark wrote: > > From: Rob Clark > > If a GEM object is allocated, and then exported as a dma-buf fd which is > mmap'd before or without the GEM buffer being directly mmap'd, the > vma_node could be unitialized. This leads to a situation where the CPU > mapping

[PATCH] drm/msm: Ensure mmap offset is initialized

From: Rob Clark If a GEM object is allocated, and then exported as a dma-buf fd which is mmap'd before or without the GEM buffer being directly mmap'd, the vma_node could be unitialized. This leads to a situation where the CPU mapping is not correctly torn down in drm_vma_node_unmap(). Fixes: