From: Jinjie Ruan <ruanjinjie@huawei.com>
To: <christian.koenig@amd.com>, <ray.huang@amd.com>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <airlied@gmail.com>, <simona@ffwll.ch>,
<karolina.stolarek@intel.com>, <Arunpravin.PaneerSelvam@amd.com>,
<thomas.hellstrom@linux.intel.com>, <asomalap@amd.com>,
<quic_jjohnson@quicinc.com>, <dri-devel@lists.freedesktop.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] drm/ttm/tests: Fix memory leak in ttm_tt_simple_create()
Date: Thu, 7 Nov 2024 09:33:27 +0800 [thread overview]
Message-ID: <534caf1f-626b-252d-b08a-fc5a3cc007e9@huawei.com> (raw)
In-Reply-To: <560d2026-5785-b6b1-eb7d-3afed714d47f@huawei.com>
On 2024/10/30 10:01, Jinjie Ruan wrote:
> Gentle ping.
>
> On 2024/10/26 10:07, Jinjie Ruan wrote:
>> modprobe ttm_device_test and then rmmod ttm_device_test, the following
>> memory leaks occurs:
>>
>> The ttm->pages allocated in ttm_tt_init() is not freed after calling
>> ttm_tt_simple_create(), which cause the memory leak:
>>
>> unreferenced object 0xffffff80caf27750 (size 8):
>> comm "kunit_try_catch", pid 2242, jiffies 4295055735
>> hex dump (first 8 bytes):
>> c0 1e 3d c3 fe ff ff ff ..=.....
>> backtrace (crc 3d11615a):
>> [<000000007f57312a>] kmemleak_alloc+0x34/0x40
>> [<000000008c6c4c7e>] __kmalloc_node_noprof+0x304/0x3e4
>> [<00000000679c1182>] __kvmalloc_node_noprof+0x1c/0x144
>> [<000000006aed0a3d>] ttm_tt_init+0x138/0x28c [ttm]
>> [<000000005c331998>] drm_gem_shmem_free+0x60/0x534 [drm_shmem_helper]
>> [<0000000022b4f375>] kunit_try_run_case+0x13c/0x3ac
>> [<00000000c525d725>] kunit_generic_run_threadfn_adapter+0x80/0xec
>> [<000000002db94a1f>] kthread+0x2e8/0x374
>> [<000000002c457ad7>] ret_from_fork+0x10/0x20
>> ......
>>
>> Fix it by calling ttm_tt_fini() in the exit function.
>>
>> Cc: stable@vger.kernel.org
>> Fixes: e6f7c641fae3 ("drm/ttm/tests: Add tests for ttm_tt")
>> Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
Hi, Nirmoy,
could this patch be merged?
>> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
>> ---
>> v4:
>> - Split out to be alone.
>> v3:
>> - s/fllowing/following/
>> v2:
>> - Add Reviewed-by.
>> ---
>> drivers/gpu/drm/ttm/tests/ttm_kunit_helpers.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/gpu/drm/ttm/tests/ttm_kunit_helpers.c b/drivers/gpu/drm/ttm/tests/ttm_kunit_helpers.c
>> index b91c13f46225..9ff216ec58ef 100644
>> --- a/drivers/gpu/drm/ttm/tests/ttm_kunit_helpers.c
>> +++ b/drivers/gpu/drm/ttm/tests/ttm_kunit_helpers.c
>> @@ -54,6 +54,7 @@ static struct ttm_tt *ttm_tt_simple_create(struct ttm_buffer_object *bo, u32 pag
>>
>> static void ttm_tt_simple_destroy(struct ttm_device *bdev, struct ttm_tt *ttm)
>> {
>> + ttm_tt_fini(ttm);
>> kfree(ttm);
>> }
>>
prev parent reply other threads:[~2024-11-07 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 2:07 Jinjie Ruan
2024-10-30 2:01 ` Jinjie Ruan
2024-11-07 1:33 ` Jinjie Ruan [this message]
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=534caf1f-626b-252d-b08a-fc5a3cc007e9@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=airlied@gmail.com \
--cc=asomalap@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=karolina.stolarek@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=ray.huang@amd.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®