linux-kernel - Possible regression in drm/i915 driver: memleak

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <f849cc70-b21f-6476-ba26-08989d1243c2@alu.unizg.hr>
Date:   Tue, 20 Dec 2022 15:33:28 +0100
From:   Mirsad Todorovac <mirsad.todorovac@....unizg.hr>
To:     LKML <linux-kernel@...r.kernel.org>
Cc:     Thorsten Leemhuis <regressions@...mhuis.info>,
        srinivas pandruvada <srinivas.pandruvada@...ux.intel.com>
Subject: Possible regression in drm/i915 driver: memleak

Hi all,

I have been unsuccessful to find any particular Intel i915 maintainer 
emails, so my best bet is to post here, as you will must assuredly 
already know them.

The problem is a kernel memory leak that is repeatedly occurring 
triggered during the execution of Chrome browser under the latest 6.1.0+ 
kernel of this morning and Almalinux 8.6 on a Lenovo desktop box
with Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz CPU.

The build is with KMEMLEAK, KASAN and MGLRU turned on during the build, 
on a vanilla mainline kernel from Mr. Torvalds' tree.

The leaks look like this one:

unreferenced object 0xffff888131754880 (size 64):
   comm "chrome", pid 13058, jiffies 4298568878 (age 3708.084s)
   hex dump (first 32 bytes):
     01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
     00 00 00 00 00 00 00 00 00 80 1e 3e 83 88 ff ff  ...........>....
   backtrace:
     [<ffffffff9e9b5542>] slab_post_alloc_hook+0xb2/0x340
     [<ffffffff9e9bbf5f>] __kmem_cache_alloc_node+0x1bf/0x2c0
     [<ffffffff9e8f767a>] kmalloc_trace+0x2a/0xb0
     [<ffffffffc08dfde5>] drm_vma_node_allow+0x45/0x150 [drm]
     [<ffffffffc0b33315>] __assign_mmap_offset_handle+0x615/0x820 [i915]
     [<ffffffffc0b34057>] i915_gem_mmap_offset_ioctl+0x77/0x110 [i915]
     [<ffffffffc08bc5e1>] drm_ioctl_kernel+0x181/0x280 [drm]
     [<ffffffffc08bc9cd>] drm_ioctl+0x2dd/0x6a0 [drm]
     [<ffffffff9ea54744>] __x64_sys_ioctl+0xc4/0x100
     [<ffffffff9fbc0178>] do_syscall_64+0x58/0x80
     [<ffffffff9fc000aa>] entry_SYSCALL_64_after_hwframe+0x72/0xdc

The complete list of leaks in attachment, but they seem similar or the same.

Please find attached lshw and kernel build config file.

I will probably check the same parms on my laptop at home, which is also 
Lenovo, but a different hw config and Ubuntu 22.10.

Thanks,
Mirsad

-- 
Mirsad Goran Todorovac
Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu
-- 
System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb, Republic of Croatia
View attachment "6.1.0+-kmemleak-chrome-i915-drm.log" of type "text/x-log" (30198 bytes)

Download attachment "lshw.txt.xz" of type "application/x-xz" (4628 bytes)

Download attachment "config-6.1.0+.xz" of type "application/x-xz" (57168 bytes)