linux-kernel - Re: WARNING: at mm/bootmem.c:535 alloc_arch_preferred

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 01 Jul 2009 08:58:29 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Christian Kujau <lists@...dbynature.de>,
	LKML <linux-kernel@...r.kernel.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"mingo@...e.hu" <mingo@...e.hu>, xen-devel@...ts.xensource.com
Subject: Re: WARNING: at mm/bootmem.c:535 alloc_arch_preferred_bootmem

Hi Jeremy,

On Tue, 2009-06-30 at 13:59 -0700, Jeremy Fitzhardinge wrote:
> > >From dc231c59194a973b80e6932bb4c162f2076635cb Mon Sep 17 00:00:00 2001
> > From: Pekka Enberg <penberg@...helsinki.fi>
> > Date: Tue, 30 Jun 2009 11:35:19 +0300
> > Subject: [PATCH] xen: Use kcalloc() in xen_init_IRQ()
> >
> > The init_IRQ() function is now called with slab allocator initialized.
> > Therefore, we must not use the bootmem allocator in xen_init_IRQ().
> > Fixes the following boot-time warning:
> >
> >   [    0.000000] Linux version 2.6.30 (dummy@sid) (gcc version 4.4.0 (Debian 4.4.0-8) ) #1 Tue Jun 23 02:13:42 CEST 2009
> >   [    0.000000] Command line: root=/dev/xvda1 console=hvc0 init=/sbin/init
> >   [    0.000000] KERNEL supported cpus:
> >   [    0.000000]   Intel GenuineIntel
> >   [    0.000000]   AMD AuthenticAMD
> >   [    0.000000]   Centaur CentaurHauls
> >   [    0.000000] BIOS-provided physical RAM map:
> >   [    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
> >   [    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
> >   [    0.000000]  Xen: 0000000000100000 - 0000000008000000 (usable)
> >   [    0.000000] DMI not present or invalid.
> >   [    0.000000] last_pfn = 0x8000 max_arch_pfn = 0x400000000
> >   [    0.000000] initial memory mapped : 0 - 20000000
> >
> > Reported-by: Christian Kujau <lists@...dbynature.de>
> > Signed-off-by: Pekka Enberg <penberg@...helsinki.fi>
> 
> Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>

Thanks! Who should pick this patch up, btw? I think it ought to go to
the xen subsystem tree (wherever that is).

			Pekka

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