Hi,

After 6.16, there has been lots of kmemleak splash like for instance:

cat /sys/kernel/debug/kmemleak
unreferenced object 0xffff888107f05800 (size 1024):
comm "(udev-worker)", pid 1495, jiffies 4294719200
hex dump (first 32 bytes):
d8 48 88 c1 ff ff ff ff 00 80 3e 00 00 00 00 00 .H........>.....
00 80 3e 00 00 00 00 00 00 14 00 00 00 00 00 00 ..>.............
backtrace (crc adb46b12):
__kmalloc_node_noprof+0x45c/0x600
vmw_surface_dirty_alloc+0xfb/0x270 [vmwgfx]
vmw_gb_surface_define_internal.constprop.0+0xd0e/0x16c0 [vmwgfx]
vmw_dumb_create+0x2e5/0xae0 [vmwgfx]
drm_client_framebuffer_create+0x168/0x3a0
drm_fbdev_ttm_driver_fbdev_probe+0x1ef/0x660 [drm_ttm_helper]
drm_fb_helper_single_fb_probe+0x1de/0x570
__drm_fb_helper_initial_config_and_unlock+0xb8/0x240
drm_fbdev_client_hotplug+0x164/0x1e0
drm_client_register+0x16a/0x240
drm_fbdev_client_setup+0x114/0x370
drm_client_setup+0x10c/0x160
vmw_probe+0x117/0x370 [vmwgfx]
local_pci_probe+0xee/0x1a0
pci_call_probe+0x17d/0x4c0
pci_device_probe+0x177/0x2c0

It happens just booting up a graphical environment in a VM under vmware player 
or ESXi.

I have bisected it to:

965544150d1cadf0e8f5bb6c13c19697e46e1429 is the first bad commit
commit 965544150d1cadf0e8f5bb6c13c19697e46e1429
Author: Zack Rusin <[email protected]>
Date:   Fri Mar 7 07:57:38 2025 -0500

    drm/vmwgfx: Refactor cursor handling


And this seems to be present with 7.0-rc1 also. 


--Mika

Reply via email to