Am 29.10.21 um 04:15 schrieb guangming@mediatek.com:
From: Guangming Cao
On Fri, 2021-10-08 at 12:24 +0200, Christian König wrote:
Am 08.10.21 um 09:54 schrieb guangming@mediatek.com:
From: Guangming Cao
Because dma-buf.name can be freed in func: "dma_buf_set_name",
so, we need t
From: Guangming Cao
On Fri, 2021-10-08 at 12:24 +0200, Christian König wrote:
> Am 08.10.21 um 09:54 schrieb guangming@mediatek.com:
> > From: Guangming Cao
> >
> > Because dma-buf.name can be freed in func: "dma_buf_set_name",
> > so, we need to acquire lock first before we read/write dma_
From: Guangming Cao
> Am 08.10.21 um 09:54 schrieb guangming@mediatek.com:
> > From: Guangming Cao
> >
> > Because dma-buf.name can be freed in func: "dma_buf_set_name",
> > so, we need to acquire lock first before we read/write dma_buf.name
> > to prevent Use After Free(UAF) issue.
> >
> >
Am 08.10.21 um 09:54 schrieb guangming@mediatek.com:
From: Guangming Cao
Because dma-buf.name can be freed in func: "dma_buf_set_name",
so, we need to acquire lock first before we read/write dma_buf.name
to prevent Use After Free(UAF) issue.
Signed-off-by: Guangming Cao
Reviewed-by: Chr
From: Guangming Cao
Because dma-buf.name can be freed in func: "dma_buf_set_name",
so, we need to acquire lock first before we read/write dma_buf.name
to prevent Use After Free(UAF) issue.
Signed-off-by: Guangming Cao
---
drivers/dma-buf/dma-buf.c | 3 +++
1 file changed, 3 insertions(+)
diff
From: Guangming Cao
Because dma-buf.name can be freed in func: "dma_buf_set_name",
so, we need to acquire lock first before we read/write dma_buf.name
to prevent Use After Free(UAF) issue.
Signed-off-by: Guangming Cao
---
drivers/dma-buf/dma-buf.c | 5 +
1 file changed, 5 insertions(+)
di
