From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: lizf@cn.fujitsu.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Leaks in trace reported by kmemleak
Date: Thu, 15 Oct 2009 10:59:13 +0200 [thread overview]
Message-ID: <c4e36d110910150159j6092d0d1lb20434bd9d43d8ce@mail.gmail.com> (raw)
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
next reply other threads:[~2009-10-15 8:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 8:59 Zdenek Kabelac [this message]
2009-10-15 9:46 ` Li Zefan
2009-10-15 11:22 ` Catalin Marinas
2009-10-16 7:45 ` Zdenek Kabelac
2009-10-16 10:57 ` Catalin Marinas
2009-10-16 13:32 ` Zdenek Kabelac
2009-10-16 14:11 ` Catalin Marinas
2009-10-16 14:28 ` Zdenek Kabelac
2009-10-16 15:07 ` Zdenek Kabelac
2009-10-16 15:31 ` Catalin Marinas
2009-10-16 16:41 ` Catalin Marinas
2009-10-19 9:15 ` Zdenek Kabelac
2009-10-19 12:00 ` Catalin Marinas
2009-10-19 13:20 ` Catalin Marinas
2009-10-20 9:58 ` Zdenek Kabelac
2009-10-20 17:03 ` Catalin Marinas
2009-10-22 13:09 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4e36d110910150159j6092d0d1lb20434bd9d43d8ce@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®