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: <c4e36d110909290218g3f98c595kaa15566b94527f04@mail.gmail.com>
Date:	Tue, 29 Sep 2009 11:18:53 +0200
From:	Zdenek Kabelac <zdenek.kabelac@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc:	len.brown@...el.com, bjorn.helgaas@...com
Subject: ACPI boot memory leaks in 2.6.32-rc1/2

Hi

My qemu guest seems to be reporting now 46 memleaks  ACPI related.

My kernel   x86_64 - commit: 17d857be649a21ca90008c6dc425d849fa83db5c
(2.6.32-rc1)


unreferenced object 0xffff88001f8095d0 (size 8):
  comm "swapper", pid 1, jiffies 4294877484
  hex dump (first 8 bytes):
    5c 00 80 1f 00 88 ff ff                          \.......
  backtrace:
    [<ffffffff8140a0c6>] kmemleak_alloc+0x26/0x60
    [<ffffffff81128253>] __kmalloc+0x153/0x250
    [<ffffffff812bfff5>] acpi_os_allocate+0x25/0x27
    [<ffffffff812c0037>] acpi_ut_initialize_buffer+0x40/0x71
    [<ffffffff812b739b>] acpi_ns_handle_to_pathname+0x3f/0xa7
    [<ffffffff812b84c4>] acpi_get_name+0x45/0xb8
    [<ffffffff8129b854>] acpi_bus_scan+0x3e/0xa0
    [<ffffffff81878acd>] acpi_scan_init+0x45/0xba
    [<ffffffff81878906>] acpi_init+0x21f/0x26a
    [<ffffffff8100904c>] do_one_initcall+0x3c/0x1d0
    [<ffffffff818574e6>] kernel_init+0x150/0x1a6
    [<ffffffff8100d21a>] child_rip+0xa/0x20
    [<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88001fa13380 (size 128):
  comm "swapper", pid 1, jiffies 4294877495
  hex dump (first 32 bytes):
    7d 00 00 00 50 43 49 30 06 00 00 00 00 0f 01 ff  }...PCI0........
    ff ff ff ff ff ff ff ff ff ff ff ff 00 00 00 00  ................
  backtrace:
    [<ffffffff8140a0c6>] kmemleak_alloc+0x26/0x60
    [<ffffffff81128253>] __kmalloc+0x153/0x250
    [<ffffffff812b829f>] acpi_get_object_info+0x161/0x341
    [<ffffffff8129afcc>] acpi_add_single_object+0x2b8/0x9ca
    [<ffffffff8129b7be>] acpi_bus_check_add+0xe0/0x138
    [<ffffffff812b98b4>] acpi_ns_walk_namespace+0xb2/0x127
    [<ffffffff812b6524>] acpi_walk_namespace+0x78/0xb2
    [<ffffffff8129b89d>] acpi_bus_scan+0x87/0xa0
    [<ffffffff81878acd>] acpi_scan_init+0x45/0xba
    [<ffffffff81878906>] acpi_init+0x21f/0x26a
    [<ffffffff8100904c>] do_one_initcall+0x3c/0x1d0
    [<ffffffff818574e6>] kernel_init+0x150/0x1a6
    [<ffffffff8100d21a>] child_rip+0xa/0x20
    [<ffffffffffffffff>] 0xffffffffffffffff
....

All seems to be acpi_bus_scan() related.

Zdenek
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ