Bug 23712 - kmemleak in cpufreq_register_driver
Summary: kmemleak in cpufreq_register_driver
Status: CLOSED CODE_FIX
Alias: None
Product: Power Management
Classification: Unclassified
Component: cpufreq (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: cpufreq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-25 08:48 UTC by Toralf Förster
Modified: 2011-07-30 06:26 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.36.1
Subsystem:
Regression: No
Bisected commit-id:

Attachments
kmemleak (25.40 KB, text/plain)
2010-11-25 08:48 UTC, Toralf Förster 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Toralf Förster 2010-11-25 08:48:42 UTC 
Created attachment 38162 [details]
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.
Comment 1 Chris Wilson 2010-12-16 15:04:53 UTC 
*** Bug 23702 has been marked as a duplicate of this bug. ***
Comment 2 Toralf Förster 2011-03-16 20:40:12 UTC 
solved in 2.6.38
Note You need to log in before you can comment on or make changes to this bug.