From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org,
"Andrey Grodzovsky" <andrey.grodzovsky@amd.com>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, "Huang Rui" <ray.huang@amd.com>,
dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [Intel-gfx] [PATCH 3/4] drm/ttm: Don't leak a resource on eviction error
Date: Thu, 22 Jun 2023 16:08:32 +0200 [thread overview]
Message-ID: <3a089ebb-7389-3d3e-beb0-13a8d64eb04d@linux.intel.com> (raw)
In-Reply-To: <ZJRSyp7fT6VXpow7@ashyti-mobl2.lan>
On 6/22/23 15:55, Andi Shyti wrote:
> Hi Thomas,
>
> On Thu, Jun 22, 2023 at 12:14:11PM +0200, Thomas Hellström wrote:
>> On eviction errors other than -EMULTIHOP we were leaking a resource.
>> Fix.
>>
>> Fixes: 403797925768 ("drm/ttm: Fix multihop assert on eviction.")
>> Cc: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
>> Cc: Christian König <christian.koenig@amd.com>
>> Cc: Christian Koenig <christian.koenig@amd.com>
>> Cc: Huang Rui <ray.huang@amd.com>
>> Cc: dri-devel@lists.freedesktop.org
>> Cc: <stable@vger.kernel.org> # v5.15+
>> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> ---
>> drivers/gpu/drm/ttm/ttm_bo.c | 16 ++++++++--------
>> 1 file changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
>> index 615d30c4262d..89530f2a027f 100644
>> --- a/drivers/gpu/drm/ttm/ttm_bo.c
>> +++ b/drivers/gpu/drm/ttm/ttm_bo.c
>> @@ -462,14 +462,14 @@ static int ttm_bo_evict(struct ttm_buffer_object *bo,
>> ret = ttm_bo_handle_move_mem(bo, evict_mem, true, ctx, &hop);
>> if (ret == -EMULTIHOP) {
>> ret = ttm_bo_bounce_temp_buffer(bo, &evict_mem, ctx, &hop);
>> - if (ret) {
>> - if (ret != -ERESTARTSYS && ret != -EINTR)
>> - pr_err("Buffer eviction failed\n");
>> - ttm_resource_free(bo, &evict_mem);
>> - goto out;
>> - }
>> - /* try and move to final place now. */
>> - goto bounce;
>> + if (!ret)
>> + /* try and move to final place now. */
>> + goto bounce;
> As we are at this, can't we replace this with a while()? Goto's
> used instead of a while loop are a fist in the eye...
I'm completely OK with that. this patch already did away with one of
them. Let's hear Christian's opinion first, though.
Thanks,
Thomas
>
> It looks even better:
>
> while (1) {
> ret = ttm_bo_handle_move_mem(bo, evict_mem, true, ctx, &hop);
> if (!ret)
> break;
>
> if (ret == -EMULTIHOP)
> ret = ttm_bo_bounce_temp_buffer(bo, &evict_mem,
> ctx, &hop);
>
> /* try again */
> if (!ret)
> continue;
>
> ttm_resource_free(bo, &evict_mem);
> if (ret != -ERESTARTSYS && ret != -EINTR)
> pr_err("Buffer eviction failed\n");
>
> break;
> }
>
> Andi
>
>> + }
>> + if (ret) {
>> + ttm_resource_free(bo, &evict_mem);
>> + if (ret != -ERESTARTSYS && ret != -EINTR)
>> + pr_err("Buffer eviction failed\n");
>> }
>> out:
>> return ret;
>> --
>> 2.40.1
next prev parent reply other threads:[~2023-06-22 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 10:14 [PATCH 0/4] drm/ttm: Fixes around resources and bulk moves Thomas Hellström
2023-06-22 10:14 ` [PATCH 1/4] drm/ttm: Fix ttm_lru_bulk_move_pos_tail() Thomas Hellström
2023-06-22 12:26 ` [Intel-gfx] " Nirmoy Das
2023-06-22 12:26 ` Christian König
2023-06-22 10:14 ` [PATCH 2/4] drm/ttm: Don't shadow the operation context Thomas Hellström
2023-06-22 10:14 ` [PATCH 3/4] drm/ttm: Don't leak a resource on eviction error Thomas Hellström
2023-06-22 12:25 ` Nirmoy Das
2023-06-22 13:55 ` [Intel-gfx] " Andi Shyti
2023-06-22 14:08 ` Thomas Hellström [this message]
2023-06-22 14:48 ` Christian König
2023-06-22 17:03 ` Thomas Hellström
2023-06-23 7:48 ` Andi Shyti
2023-06-22 10:14 ` [PATCH 4/4] drm/ttm: Don't leak a resource on swapout move error Thomas Hellström
2023-06-22 12:25 ` Nirmoy Das
2023-06-22 13:56 ` [Intel-gfx] " Andi Shyti
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=3a089ebb-7389-3d3e-beb0-13a8d64eb04d@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=andrey.grodzovsky@amd.com \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray.huang@amd.com \
--cc=stable@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