From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 23712] New: kmemleak in cpufreq_register_driver
Date: Thu, 25 Nov 2010 08:48:43 GMT [thread overview]
Message-ID: <bug-23712-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=23712
Summary: kmemleak in cpufreq_register_driver
Product: Power Management
Version: 2.5
Kernel Version: 2.6.36.1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@vger.kernel.org
ReportedBy: toralf.foerster@gmx.de
Regression: No
Created an attachment (id=38162)
--> (https://bugzilla.kernel.org/attachment.cgi?id=38162)
kmemleak
Yesterday I got the attached kmemleak after a ThinkPad T400 was waked from
s2ram:
unreferenced object 0xf5cb8b00 (size 64):
comm "modprobe", pid 1016, jiffies 4294676606 (age 39077.100s)
hex dump (first 32 bytes):
00 00 00 00 e8 a2 24 00 01 00 00 00 00 9f 24 00 ......$.......$.
02 00 00 00 00 6a 18 00 03 00 00 00 00 35 0c 00 .....j.......5..
backtrace:
[<c1253837>] kmemleak_alloc+0x27/0x50
[<c10b042f>] __kmalloc+0xbf/0x120
[<f9a807ee>] acpi_cpufreq_cpu_init+0x1ee/0x4e4 [acpi_cpufreq]
[<c11e3ef2>] cpufreq_add_dev+0x142/0x3a0
[<c11a82f7>] sysdev_driver_register+0x97/0x110
[<c11e3456>] cpufreq_register_driver+0x86/0x140
[<f9a84080>] 0xf9a84080
[<c1001130>] do_one_initcall+0x30/0x160
[<c1064909>] sys_init_module+0x99/0x1e0
[<c1002d53>] sysenter_do_call+0x12/0x22
[<ffffffff>] 0xffffffff
...
Much more are attached onto this bug report.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-11-25 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 8:48 bugzilla-daemon [this message]
2010-12-16 15:04 ` [Bug 23712] kmemleak in cpufreq_register_driver bugzilla-daemon
2011-03-16 20:40 ` bugzilla-daemon
2011-07-30 6:26 ` bugzilla-daemon
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=bug-23712-12968@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.org \
/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.