linux-kernel - Leaks in trace reported by kmemleak

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <c4e36d110910150159j6092d0d1lb20434bd9d43d8ce@mail.gmail.com>
Date:	Thu, 15 Oct 2009 10:59:13 +0200
From:	Zdenek Kabelac <zdenek.kabelac@...il.com>
To:	lizf@...fujitsu.com
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Leaks in trace reported by kmemleak

I've noticed your latest patch for memory leak in filter setting
(8ad807318fcd...) - but even with this patch - kmemleak seems to still
report  lots  (~900) of following leaks - note - they come only from
i915 and kvm module - so I'm not sure if these two modules are doing
something wrong or the problem is in trace code.

It looks like whole directory is somehow forgotten.

nreferenced object 0xffff880134b21268 (size 8):
  comm "modprobe", pid 1099, jiffies 4294881626
  hex dump (first 8 bytes):
    69 6e 74 00 01 88 ff ff                          int.....
  backtrace:
    [<ffffffff8140e986>] kmemleak_alloc+0x26/0x60
    [<ffffffff81127943>] __kmalloc_track_caller+0x143/0x230
    [<ffffffff81104385>] kstrdup+0x45/0x80
    [<ffffffff810dd5c9>] trace_define_field+0x89/0x1b0
    [<ffffffff810dd7bc>] trace_define_common_fields+0xcc/0x110
    [<ffffffffa0370426>]
ftrace_define_fields_i915_ring_wait_end+0x16/0x50 [i915]
    [<ffffffff810dcc53>] event_create_dir+0x93/0x480
    [<ffffffff810dd13f>] trace_module_notify+0xff/0x500
    [<ffffffff814247e8>] notifier_call_chain+0x78/0xb0
    [<ffffffff8107f190>] __blocking_notifier_call_chain+0x60/0x90
    [<ffffffff8107f1d6>] blocking_notifier_call_chain+0x16/0x20
    [<ffffffff810a0bfa>] sys_init_module+0xaa/0x260
    [<ffffffff8100c11b>] system_call_fastpath+0x16/0x1b
    [<ffffffffffffffff>] 0xffffffffffffffff

...

unreferenced object 0xffff880134b21a78 (size 8):
  comm "modprobe", pid 1106, jiffies 4294881716
  hex dump (first 8 bytes):
    5f 5f 75 33 32 00 ff ff                          __u32...
  backtrace:
    [<ffffffff8140e986>] kmemleak_alloc+0x26/0x60
    [<ffffffff81127943>] __kmalloc_track_caller+0x143/0x230
    [<ffffffff81104385>] kstrdup+0x45/0x80
    [<ffffffff810dd5c9>] trace_define_field+0x89/0x1b0
    [<ffffffffa03cf802>]
ftrace_define_fields_kvm_mmu_pagetable_walk+0x82/0x90 [kvm]
    [<ffffffff810dcc53>] event_create_dir+0x93/0x480
    [<ffffffff810dd13f>] trace_module_notify+0xff/0x500
    [<ffffffff814247e8>] notifier_call_chain+0x78/0xb0
    [<ffffffff8107f190>] __blocking_notifier_call_chain+0x60/0x90
    [<ffffffff8107f1d6>] blocking_notifier_call_chain+0x16/0x20
    [<ffffffff810a0bfa>] sys_init_module+0xaa/0x260
    [<ffffffff8100c11b>] system_call_fastpath+0x16/0x1b
    [<ffffffffffffffff>] 0xffffffffffffffff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/