From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Monk Liu <Monk.Liu@amd.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma-buf/reservation: shouldn't kfree staged when slot available
Date: Wed, 28 Feb 2018 09:26:46 +0100 [thread overview]
Message-ID: <fa9f8ade-000f-a9b5-0bc9-0dd3f10d9722@gmail.com> (raw)
In-Reply-To: <1519800242-2442-1-git-send-email-Monk.Liu@amd.com>
Am 28.02.2018 um 07:44 schrieb Monk Liu:
> under below scenario the obj->fence would refer to a wild pointer:
>
> 1,call reservation_object_reserved_shared
> 2,call reservation_object_add_shared_fence
> 3,call reservation_object_reserved_shared
> 4,call reservation_object_add_shared_fence
>
> in step 1, staged is allocated,
>
> in step 2, code path will go reservation_object_add_shared_replace()
> and obj->fence would be assigned as staged (through RCU_INIT_POINTER)
>
> in step 3, obj->staged will be freed(by simple kfree),
> which make obj->fence point to a wild pointer...
Well that explanation is still nonsense. See
reservation_object_add_shared_fence:
> obj->staged = NULL;
Among the first things reservation_object_add_shared_fence() does is it
sets obj->staged to NULL.
So step 3 will not free anything and we never have a wild pointer.
Regards,
Christian.
>
> in step 4, code path will go reservation_object_add_shared_inplace()
> and inside it the @fobj (which equals to @obj->staged, set by above steps)
> is already a wild pointer
>
> should remov the kfree on staged in reservation_object_reserve_shared()
>
> Change-Id: If7c01f1b4be3d3d8a81efa90216841f79ab1fc1c
> Signed-off-by: Monk Liu <Monk.Liu@amd.com>
> ---
> drivers/dma-buf/reservation.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/dma-buf/reservation.c b/drivers/dma-buf/reservation.c
> index 375de41..b473ccc 100644
> --- a/drivers/dma-buf/reservation.c
> +++ b/drivers/dma-buf/reservation.c
> @@ -74,12 +74,9 @@ int reservation_object_reserve_shared(struct reservation_object *obj)
> old = reservation_object_get_list(obj);
>
> if (old && old->shared_max) {
> - if (old->shared_count < old->shared_max) {
> - /* perform an in-place update */
> - kfree(obj->staged);
> - obj->staged = NULL;
> + if (old->shared_count < old->shared_max)
> return 0;
> - } else
> + else
> max = old->shared_max * 2;
> } else
> max = 4;
next prev parent reply other threads:[~2018-02-28 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 6:44 Monk Liu
2018-02-28 8:26 ` Christian König [this message]
2018-03-05 7:55 ` Liu, Monk
2018-03-05 11:22 ` Christian König
2018-03-05 11:25 ` Liu, Monk
2018-03-05 11:28 ` Christian König
2018-03-05 11:37 ` Liu, Monk
2018-03-05 11:39 ` Christian König
2018-03-05 11:47 ` Liu, Monk
2018-03-05 11:51 ` Christian König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa9f8ade-000f-a9b5-0bc9-0dd3f10d9722@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Monk.Liu@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome