From: Larry Finger <Larry.Finger@lwfinger.net>
To: "zhangwei(Jovi)" <jovi.zhangwei@huawei.com>,
Steven Rostedt <srostedt@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: V3.10-rc1 memory leak
Date: Mon, 13 May 2013 12:39:51 -0500 [thread overview]
Message-ID: <51912567.6090507@lwfinger.net> (raw)
Using v3.10-rc1-68-g2d3ec09, I am getting many instances of the following from
kmemleak:
unreferenced object 0xffff8800b546dc30 (size 48):
comm "systemd-udevd", pid 2181, jiffies 4294899141 (age 274.096s)
hex dump (first 32 bytes):
00 dc 46 b5 00 88 ff ff d0 ff 5b a0 ff ff ff ff ..F.......[.....
1c 3b 5b a0 ff ff ff ff 12 3a 5b a0 ff ff ff ff .;[......:[.....
backtrace:
[<ffffffff81432e81>] kmemleak_alloc+0x21/0x50
[<ffffffff81143c2b>] kmem_cache_alloc+0x11b/0x270
[<ffffffff810e9ee0>] __trace_define_field+0x40/0xd0
[<ffffffff810e9fc5>] trace_define_field+0x55/0x70
[<ffffffffa05e6ba0>] 0xffffffffa05e6ba0
[<ffffffff810ea735>] event_create_dir+0x2e5/0x480
[<ffffffff810ea920>] __trace_add_new_event+0x50/0x80
[<ffffffff810eacf9>] __add_event_to_tracers+0x69/0xc0
[<ffffffff810eb4e1>] trace_module_notify+0x1e1/0x2f0
[<ffffffff8106e8f5>] notifier_call_chain+0x55/0x110
[<ffffffff8106eb27>] __blocking_notifier_call_chain+0x67/0xc0
[<ffffffff8106eb91>] blocking_notifier_call_chain+0x11/0x20
[<ffffffff810af792>] load_module+0x19e2/0x24b0
[<ffffffff810b0317>] SyS_init_module+0xb7/0xe0
[<ffffffff814499d2>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
These appear to be real leaks, but I am not familiar with this section of the
code, and they could be false indications.
This mail is sent to all authors of patches incorporated in
kernel/trace/trace_events.c in 2013. Kernel 3.9 did not show this problem.
Thanks,
Larry
next reply other threads:[~2013-05-13 17:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 17:39 Larry Finger [this message]
2013-05-14 19:09 ` V3.10-rc1 memory leak Steven Rostedt
2013-05-14 20:30 ` Catalin Marinas
2013-05-14 21:10 ` Larry Finger
2013-05-14 21:20 ` Steven Rostedt
2013-05-15 0:57 ` Steven Rostedt
2013-05-15 3:15 ` Larry Finger
2013-05-15 15:02 ` Catalin Marinas
2013-05-15 15:49 ` Toshi Kani
2013-05-15 16:47 ` Catalin Marinas
2013-05-15 17:53 ` Toshi Kani
2013-05-15 20:46 ` Larry Finger
2013-05-15 14:37 ` Catalin Marinas
2013-05-15 19:33 ` Steven Rostedt
2013-05-15 19:46 ` Steven Rostedt
2013-05-16 10:12 ` Catalin Marinas
2013-05-16 23:47 ` Rusty Russell
2013-05-14 20:36 ` Larry Finger
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=51912567.6090507@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=jovi.zhangwei@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=srostedt@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.