linux-kernel - Re: 2.6.22-rc1-mm1 - Call trace in slub

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 May 2007 18:22:24 +0530
From:	"Satyam Sharma" <satyam.sharma@...il.com>
To:	"Reuben Farrelly" <reuben-linuxkernel@...b.net>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, clameter@....com
Subject: Re: 2.6.22-rc1-mm1 - Call trace in slub_def.h

On 5/17/07, Reuben Farrelly <reuben-linuxkernel@...b.net> wrote:
> [...]
> I have just seen this on boot, with 2.6.22-rc2-mm1 on x86_64:
> [...]
> BUG: at include/linux/slub_def.h:88 kmalloc_index()
>
> Call Trace:
>   [<ffffffff8034f3f9>] pci_dev_put+0x12/0x14
>   [<ffffffff80283f30>] get_slab+0xb5/0x265
>   [<ffffffff802841bc>] __kmalloc+0x13/0xa3
>   [<ffffffff8021a4aa>] cache_k8_northbridges+0x80/0x116
>   [<ffffffff8063fed2>] gart_iommu_init+0x16/0x594
>   [<ffffffff804562ac>] genl_rcv+0x0/0x68
>   [<ffffffff804548ed>] netlink_kernel_create+0x15e/0x16b
>   [<ffffffff804acc52>] mutex_unlock+0x9/0xb
>   [<ffffffff80639fad>] pci_iommu_init+0x9/0x12
>   [<ffffffff806306af>] kernel_init+0x152/0x322
>   [<ffffffff80249c7c>] trace_hardirqs_on+0xc0/0x14e
>   [<ffffffff804ae03d>] trace_hardirqs_on_thunk+0x35/0x37
>   [<ffffffff80249c7c>] trace_hardirqs_on+0xc0/0x14e
>   [<ffffffff8020a848>] child_rip+0xa/0x12
>   [<ffffffff80209f5c>] restore_args+0x0/0x30
>   [<ffffffff8063055d>] kernel_init+0x0/0x322
>   [<ffffffff8020a83e>] child_rip+0x0/0x12
>
> PCI-GART: No AMD northbridge found.
> hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
> hpet0: 3 64-bit timers, 14318180 Hz
> ACPI: RTC can wake from S4
> pnp: 00:01: iomem range 0xf0000000-0xf3ffffff has been reserved
> pnp: 00:01: iomem range 0xfed13000-0xfed13fff has been reserved

This ( http://lkml.org/lkml/2007/5/16/350 ) patch by Ben Collins
submitted yesterday should take care of this.

Thanks,
Satyam
-
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/