While debugging some other bits, I did a reboot -d followed by ::findleaks. I
run KVM on this particular machine, and ::findleaks found some possible KVM
leaks.
NOTE: I did these with moddebug set to 0x20000, which makes _fini() returrn
EBUSY, which means the driver text won't unload. I think this is kvm
(mis)behaving under a pre-qemu-launch incantation of "devfsadm".
Thanks,
Dan
=======================
kmem_alloc_96 leak: 1 buffer, 96 bytes
ADDR BUFADDR TIMESTAMP THREAD
CACHE LASTLOG CONTENTS
ffffff1212cca300 ffffff1210a6e178 6def10995f3a0 ffffff007c22ac40
ffffff113642ca88 ffffff1174c31180 ffffff119c187d18
kmem_cache_alloc_debug+0x2e0
kmem_cache_alloc+0xdd
kmem_alloc+0x4b
alloc_kvm_area+0x22
vmx_hardware_setup+0xe3
kvm_arch_hardware_setup+0xe
kvm_init+0x43
vmx_init+0x161
kvm_attach+0xd9
devi_attach+0x9e
attach_node+0x14f
i_ndi_config_node+0xc0
i_ddi_attachchild+0x88
devi_attach_node+0x88
config_immediate_children+0x127
kmem_alloc_96 leak: 1 buffer, 96 bytes
ADDR BUFADDR TIMESTAMP THREAD
CACHE LASTLOG CONTENTS
ffffff1214ec5dc0 ffffff1214d74000 6def10995f76d ffffff007c22ac40
ffffff113642ca88 ffffff1174c31240 0
kmem_cache_alloc_debug+0x2e0
kmem_cache_alloc+0x320
kmem_alloc+0x4b
alloc_kvm_area+0x3e
vmx_hardware_setup+0xe3
kvm_arch_hardware_setup+0xe
kvm_init+0x43
vmx_init+0x161
kvm_attach+0xd9
devi_attach+0x9e
attach_node+0x14f
i_ndi_config_node+0xc0
i_ddi_attachchild+0x88
devi_attach_node+0x88
config_immediate_children+0x127
kmem_alloc_96 leak: 1 buffer, 96 bytes
ADDR BUFADDR TIMESTAMP THREAD
CACHE LASTLOG CONTENTS
ffffff1216e6d808 ffffff1216bf0f80 6def109965200 ffffff007c22ac40
ffffff113642ca88 ffffff1174c313c0 0
kmem_cache_alloc_debug+0x2e0
kmem_cache_alloc+0x320
kmem_alloc+0x4b
alloc_kvm_area+0x5a
vmx_hardware_setup+0xe3
kvm_arch_hardware_setup+0xe
kvm_init+0x43
vmx_init+0x161
kvm_attach+0xd9
devi_attach+0x9e
attach_node+0x14f
i_ndi_config_node+0xc0
i_ddi_attachchild+0x88
devi_attach_node+0x88
config_immediate_children+0x127
kmem_alloc_96 leak: 1 buffer, 96 bytes
ADDR BUFADDR TIMESTAMP THREAD
CACHE LASTLOG CONTENTS
ffffff1216e6d8e0 ffffff1216bf0f08 6def109965426 ffffff007c22ac40
ffffff113642ca88 ffffff1174c31480 0
kmem_cache_alloc_debug+0x2e0
kmem_cache_alloc+0x320
kmem_alloc+0x4b
alloc_kvm_area+0x76
vmx_hardware_setup+0xe3
kvm_arch_hardware_setup+0xe
kvm_init+0x43
vmx_init+0x161
kvm_attach+0xd9
devi_attach+0x9e
attach_node+0x14f
i_ndi_config_node+0xc0
i_ddi_attachchild+0x88
devi_attach_node+0x88
config_immediate_children+0x127
kmem_alloc_320 leak: 2 buffers, 320 bytes each, 640 bytes total
ADDR BUFADDR TIMESTAMP THREAD
CACHE LASTLOG CONTENTS
ffffff11fd1f0a28 ffffff11fd1d2480 6def1099669de ffffff007c22ac40
ffffff1136430008 ffffff1174c31600 ffffff119c1e35c0
kmem_cache_alloc_debug+0x2e0
kmem_cache_alloc+0xdd
kmem_zalloc+0x47
alloc_kvm_area+0x108
vmx_hardware_setup+0xe3
kvm_arch_hardware_setup+0xe
kvm_init+0x43
vmx_init+0x161
kvm_attach+0xd9
devi_attach+0x9e
attach_node+0x14f
i_ndi_config_node+0xc0
i_ddi_attachchild+0x88
devi_attach_node+0x88
config_immediate_children+0x127
kmem_alloc_320 leak: 9 buffers, 320 bytes each, 2880 bytes total
ADDR BUFADDR TIMESTAMP THREAD
CACHE LASTLOG CONTENTS
ffffff1216942738 ffffff120b44d600 6def10996abef ffffff007c22ac40
ffffff1136430008 ffffff1174c31a80 0
kmem_cache_alloc_debug+0x2e0
kmem_cache_alloc+0x320
kmem_zalloc+0x47
alloc_kvm_area+0x108
vmx_hardware_setup+0xe3
kvm_arch_hardware_setup+0xe
kvm_init+0x43
vmx_init+0x161
kvm_attach+0xd9
devi_attach+0x9e
attach_node+0x14f
i_ndi_config_node+0xc0
i_ddi_attachchild+0x88
devi_attach_node+0x88
config_immediate_children+0x127
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
