Re: [PATCH] driver:dma bug_fix : access freed memory

[Sudip Mukherjee]

On Fri, Nov 27, 2015 at 05:44:53AM +0000, êìë wrote:
> From 8f6aeb362d9e44f29d46ae7694cdfee4408406ce Mon Sep 17 00:00:00 2001
> From: "KIM JUGNBAE" <jb09.kim@xxxxxxxxxxx>
> Date: Thu, 26 Nov 2015 16:28:47 +0900
> Subject: [PATCH] bug_fix : access freed memory

This part should not be present in the patch.

> 
> sync_fenc_free & fence_check_cb_func would be executed at
> other cpu. fence_check_cb_func access freed fence memory after
> kfree(fence) at sync_fence_free.
> To escaped this issue, atomic_read(&fence->status) need to be
> protected by child_list_lock.
> 
> Signed-off-by: "kimjungbae\" " <jb09.kim@xxxxxxxxxxx>"

The From name and the Signed-off-by name shouls be same. Mayvbe you can
consider having Kim Jugnbae (or Jungbae) as both.

> ---
>  drivers/dma-buf/fence.c              |   13 +++++++++++++
>  drivers/staging/android/sync.c       |   10 +++++++---
>  drivers/staging/android/sync_debug.c |    2 ++
>  include/linux/fence.h                |    1 +
>  4 files changed, 23 insertions(+), 3 deletions(-)

Usually staging patches can not touch anything outside staging.

regards
sudip
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/