All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Koenig, Christian" <Christian.Koenig@amd.com>
To: Dmitry Osipenko <digetx@gmail.com>, Eric Anholt <eric@anholt.net>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jason Ekstrand <jason@jlekstrand.net>
Subject: Re: [PATCH 2/2] drm: Revert syncobj timeline changes.
Date: Fri, 21 Dec 2018 18:45:08 +0000	[thread overview]
Message-ID: <6773eadb-5c15-8168-9bba-5e1cfd1c3194@amd.com> (raw)
In-Reply-To: <44f25278-fbbd-f95b-c2ab-87834e5d095e@gmail.com>

Am 21.12.18 um 19:35 schrieb Dmitry Osipenko:
> On 21.12.2018 21:27, Christian König wrote:
>> Am 19.12.18 um 18:53 schrieb Dmitry Osipenko:
>>> [SNIP]
>>>> @@ -931,9 +718,6 @@ static signed long drm_syncobj_array_wait_timeout(struct drm_syncobj **syncobjs,
>>>>          if (flags & DRM_SYNCOBJ_WAIT_FLAGS_WAIT_FOR_SUBMIT) {
>>>>            for (i = 0; i < count; ++i) {
>>>> -            if (entries[i].fence)
>>>> -                continue;
>>>> -
>>>>                drm_syncobj_fence_get_or_add_callback(syncobjs[i],
>>>>                                      &entries[i].fence,
>>>>                                      &entries[i].syncobj_cb,
>>> Hello,
>>>
>>> The above three removed lines we added in commit 337fe9f5c1e7de ("drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set") that fixed a memleak. Removal of the lines returns the memleak because of disbalanced fence refcounting and it looks like they were removed unintentionally in this patch.
>> That was already fixed with 61a98b1b9a8c7 drm/syncobj: remove drm_syncobj_cb and cleanup.
>>
>> This cleanup removed all the duplicate checking and is now adding the callback only once.
> Okay, though that commit is not in linux-next. I assume it will show up eventually.

Need to double check, that could indeed be a problem.

Christian.

  reply	other threads:[~2018-12-21 18:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 16:04 [PATCH 0/2] reverts to un-regress v3d Eric Anholt
2018-11-08 16:04 ` [PATCH 1/2] Revert "drm/sched: fix timeout handling v2" Eric Anholt
2018-11-08 16:04   ` Eric Anholt
2018-11-08 16:10   ` Koenig, Christian
2018-11-08 16:10     ` Koenig, Christian
2018-11-08 16:19     ` Eric Anholt
2018-11-08 16:19       ` Eric Anholt
2018-11-08 16:48       ` Koenig, Christian
2018-11-08 16:04 ` [PATCH 2/2] drm: Revert syncobj timeline changes Eric Anholt
2018-11-08 16:07   ` Koenig, Christian
2018-11-08 16:07     ` Koenig, Christian
2018-11-08 16:52     ` Christian König
2018-11-09  2:35       ` zhoucm1
2018-11-09  2:35         ` zhoucm1
2018-11-09 21:10         ` Eric Anholt
2018-11-09 21:10           ` Eric Anholt
2018-11-09 22:26           ` Eric Anholt
2018-11-09 22:26             ` Eric Anholt
2018-11-12 10:16             ` Christian König
2018-11-12 10:28               ` zhoucm1
2018-11-12 10:48               ` Chris Wilson
2018-11-12 11:47                 ` Koenig, Christian
2018-11-12 11:47                   ` Koenig, Christian
2018-11-13  5:57                 ` zhoucm1
2018-11-13  5:57                   ` zhoucm1
2018-11-13  6:18               ` zhoucm1
     [not found]                 ` <84df39ac-e8a2-f0f5-6562-f2df25c110e8@amd.com>
     [not found]                   ` <8736s4w31m.fsf@anholt.net>
     [not found]                     ` <22b7eef1-cc13-5662-5656-d39aeb0c78e0@amd.com>
     [not found]                       ` <87bm6rb0cy.fsf@anholt.net>
2018-11-15 18:47                         ` Eric Anholt
2018-12-19 17:53   ` Dmitry Osipenko
2018-12-21 18:27     ` Christian König
2018-12-21 18:35       ` Dmitry Osipenko
2018-12-21 18:45         ` Koenig, Christian [this message]
2018-12-21 18:59           ` Dmitry Osipenko

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=6773eadb-5c15-8168-9bba-5e1cfd1c3194@amd.com \
    --to=christian.koenig@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=digetx@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=jason@jlekstrand.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.