[Xen-devel] domU v3.10.x kmemleak

[William Dauchy <wdauchy@xxxxxxxxx>]

Hello,

I have activated kmemleak on a v3.10.x domU (x86_64) running on a dom0
v3.4.x (x86_32) and xen hypervisor v4.1.x
This domU is leaking pages, among other things I found this output in kmemleak:

unreferenced object 0xffff88005c9b3498 (size 560):
  comm "blkid", pid 572, jiffies 4294893852 (age 1912.348s)
  hex dump (first 32 bytes):
    02 00 00 00 00 00 00 00 c0 2d 76 59 00 88 ff ff  .........-vY....
    00 2f 24 81 ff ff ff ff 00 00 00 00 00 00 00 00  ./$.............
  backtrace:
    [<ffffffff81243aa0>] radix_tree_preload+0x30/0x90
    [<ffffffff81243aa0>] radix_tree_preload+0x30/0x90
    [<ffffffff810f6518>] kmem_cache_alloc+0x138/0x230
    [<ffffffff81243aa0>] radix_tree_preload+0x30/0x90
    [<ffffffff810bbb9b>] add_to_page_cache_locked+0x7b/0x140
    [<ffffffff810bbc71>] add_to_page_cache_lru+0x11/0x40
    [<ffffffff810c5946>] __do_page_cache_readahead+0x236/0x250
    [<ffffffff8100680b>] xen_make_pte+0x1b/0x50
    [<ffffffff810c5baf>] force_page_cache_readahead+0x8f/0xc0
    [<ffffffff810bd076>] generic_file_aio_read+0x4c6/0x6c0
    [<ffffffff81004739>] __raw_callee_save_xen_pmd_val+0x11/0x1e
    [<ffffffff8110b78a>] do_sync_read+0x6a/0xa0
    [<ffffffff8110c670>] vfs_read+0xa0/0x180
    [<ffffffff8110c901>] SyS_read+0x51/0xb0
    [<ffffffff81395369>] system_call_fastpath+0x16/0x1b
    [<ffffffffffffffff>] 0xffffffffffffffff

unreferenced object 0xffff88005af24bc0 (size 192):
  comm "softirq", pid 0, jiffies 4294894408 (age 2246.916s)
  hex dump (first 32 bytes):
    b0 d0 e6 50 00 88 ff ff 70 72 2f 81 ff ff ff ff  ...P....pr/.....
    00 00 00 00 00 00 00 00 00 50 f9 5b 00 88 ff ff  .........P.[....
  backtrace:
    [<ffffffff812d1ea6>] dst_alloc+0x56/0x180
    [<ffffffff812d1ea6>] dst_alloc+0x56/0x180
    [<ffffffff810f6518>] kmem_cache_alloc+0x138/0x230
    [<ffffffff812d1ea6>] dst_alloc+0x56/0x180
    [<ffffffff812f9b9e>] ip_route_input_noref+0x11e/0xbf0
    [<ffffffff81186ad1>] ext4_end_bio+0x251/0x2d0
    [<ffffffff810f5729>] poison_obj+0x29/0x40
    [<ffffffff812fc274>] ip_rcv_finish+0x184/0x360
    [<ffffffff812ca033>] __netif_receive_skb_core+0x5e3/0x7d0
    [<ffffffff812ca434>] netif_receive_skb+0x24/0x80
    [<ffffffff812cb7e8>] napi_gro_receive+0x98/0xd0
    [<ffffffff8129de37>] xennet_poll+0x797/0xce0
    [<ffffffff8107e91f>] clockevents_program_event+0x6f/0x110
    [<ffffffff810a7043>] handle_irq_event_percpu+0x83/0x140
    [<ffffffff812ca734>] net_rx_action+0x104/0x1c0
    [<ffffffff81042056>] __do_softirq+0xd6/0x1b0

Do you have any idea where this could come from?

Thanks,

-- 
William

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel