All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 214029] [bisected] [amdgpu] Several memory leaks in amdgpu and ttm
Date: Tue, 28 Sep 2021 15:21:20 +0000	[thread overview]
Message-ID: <bug-214029-2300-Ugs7hFgzqq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214029-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=214029

Erhard F. (erhard_f@mailbox.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |christian.koenig@amd.com

--- Comment #15 from Erhard F. (erhard_f@mailbox.org) ---
I got around skipping commits by cherry-picking
9551158069ba8fcc893798d42dc4f978b62ef60f (kfence: make compatible with
kmemleak) and finally was able to complete the bisect. The offending commit
was:

 # git bisect good
d02117f8efaa5fbc37437df1ae955a147a2a424a is the first bad commit
commit d02117f8efaa5fbc37437df1ae955a147a2a424a
Author: Christian König <christian.koenig@amd.com>
Date:   Sat Apr 17 19:09:30 2021 +0200

    drm/ttm: remove special handling for non GEM drivers

    vmwgfx is the only driver actually using this. Move the handling into
    the driver instead.

    Signed-off-by: Christian König <christian.koenig@amd.com>
    Acked-by: Huang Rui <ray.huang@amd.com>
    Reviewed-by: Zack Rusin <zackr@vmware.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20210419092853.1605-1-christian.koenig@amd.com

 drivers/gpu/drm/ttm/ttm_bo.c       | 11 -----------
 drivers/gpu/drm/vmwgfx/vmwgfx_bo.c | 10 ++++++++++
 include/drm/ttm/ttm_bo_api.h       | 19 -------------------
 3 files changed, 10 insertions(+), 30 deletions(-)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2021-09-28 15:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 18:34 [Bug 214029] New: [NAVI] Several memory leaks in amdgpu and ttm bugzilla-daemon
2021-08-10 18:35 ` [Bug 214029] " bugzilla-daemon
2021-08-10 18:36 ` bugzilla-daemon
2021-08-30 13:45 ` bugzilla-daemon
2021-08-30 13:45 ` bugzilla-daemon
2021-08-30 13:49 ` bugzilla-daemon
2021-08-31  9:39 ` bugzilla-daemon
2021-08-31 10:20 ` bugzilla-daemon
2021-09-13 19:57 ` bugzilla-daemon
2021-09-13 19:58 ` bugzilla-daemon
2021-09-13 20:00 ` bugzilla-daemon
2021-09-20 16:29 ` bugzilla-daemon
2021-09-20 16:30 ` bugzilla-daemon
2021-09-20 16:35 ` bugzilla-daemon
2021-09-20 16:35 ` [Bug 214029] [bisected] " bugzilla-daemon
2021-09-22 22:05 ` bugzilla-daemon
2021-09-22 22:05 ` [Bug 214029] [bisected] [amdgpu] " bugzilla-daemon
2021-09-28 15:21 ` bugzilla-daemon [this message]
2021-09-28 15:25 ` bugzilla-daemon
2021-10-15 22:53 ` bugzilla-daemon
2021-10-15 22:55 ` bugzilla-daemon
2021-10-20 17:46 ` bugzilla-daemon
2021-10-21  7:37 ` bugzilla-daemon
2021-10-21  8:44 ` bugzilla-daemon
2021-10-21 12:39 ` bugzilla-daemon
2021-11-03  9:45 ` bugzilla-daemon
2021-11-03 15:07 ` bugzilla-daemon
2021-11-03 17:54 ` bugzilla-daemon
2021-11-04  7:16 ` bugzilla-daemon
2021-11-04  7:44 ` bugzilla-daemon

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=bug-214029-2300-Ugs7hFgzqq@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.