From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by gabe.freedesktop.org (Postfix) with ESMTPS id 7754C10F063 for ; Fri, 4 Mar 2022 05:28:42 +0000 (UTC) From: Chuansheng Liu To: igt-dev@lists.freedesktop.org Date: Fri, 4 Mar 2022 13:15:09 +0800 Message-Id: <20220304051509.44816-1-chuansheng.liu@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [igt-dev] [PATCH i-g-t] tests/gem_mmap_gtt: add test mmap_closed_bo List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Tvrtko Ursulin Errors-To: igt-dev-bounces@lists.freedesktop.org Sender: "igt-dev" List-ID: Recently we figured out one memory leak in i915 driver when running below alike test: create_bo gem_mmap_gtt bo gem_mmap_gtt bo twice close_bo then the memory leak is detected. More details can be referred in https://patchwork.freedesktop.org/patch/475802/?series=100532&rev=2 For detecting such issue, this test case mmap_closed_bo is created, it will close the bo with keeping one mmap, then second mmap the bo, in normal situation, we expect second mmap failure with EACCESS. But it will succeed if driver has the vm_node allowance leak. Cc: Tvrtko Ursulin Signed-off-by: Chuansheng Liu --- tests/i915/gem_mmap_gtt.c | 42 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c index 92bbb5d2..0f4d5385 100644 --- a/tests/i915/gem_mmap_gtt.c +++ b/tests/i915/gem_mmap_gtt.c @@ -318,6 +318,46 @@ test_wc(int fd) 5*gtt_writes/256., 5*cpu_writes/256.); } +static void mmap_closed_bo(int fd) +{ + struct drm_i915_gem_mmap_gtt mmap_arg; + void *p1, *p2; + int loop = 0, i = 0; + + while (loop++ < 2) { + memset(&mmap_arg, 0, sizeof(mmap_arg)); + + mmap_arg.handle = gem_create(fd, OBJECT_SIZE); + igt_assert(mmap_arg.handle); + + i = loop; + while (i--) { + /* get offset, here we tries a loop to call GEM_MMAP_GTT many times, + * it could trigger driver memory leak issue easily. + */ + do_ioctl(fd, DRM_IOCTL_I915_GEM_MMAP_GTT, &mmap_arg); + } + + p1 = mmap64(0, OBJECT_SIZE, PROT_READ | PROT_WRITE, + MAP_SHARED, fd, mmap_arg.offset); + igt_assert(p1 != MAP_FAILED); + + gem_close(fd, mmap_arg.handle); + gem_quiescent_gpu(fd); + + p2 = mmap64(0, OBJECT_SIZE, PROT_READ | PROT_WRITE, + MAP_SHARED, fd, mmap_arg.offset); + + munmap(p1, OBJECT_SIZE); + + /* we expect mmapping p2 would fail, otherwise the driver + * may not clean up the allowance of vm_node, it would + * cause memory leak. + */ + igt_assert(p2 == MAP_FAILED); + } +} + static int mmap_gtt_version(int i915) { int val = 0; @@ -1305,6 +1345,8 @@ igt_main test_write(fd); igt_subtest("basic-write-gtt") test_write_gtt(fd); + igt_subtest("mmap_closed_bo") + mmap_closed_bo(fd); igt_subtest("ptrace") test_ptrace(fd); igt_subtest("coherency") -- 2.25.0.rc2