linux-kernel - Re: [bug] SLUB + mm/slab.c boot crash in -rc9

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:	Tue, 15 Apr 2008 09:41:59 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org,
	"Christoph Lameter" <clameter@....com>,
	"Mel Gorman" <mel@....ul.ie>, "Nick Piggin" <npiggin@...e.de>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, Yinghai.Lu@....com
Subject: Re: [bug] SLUB + mm/slab.c boot crash in -rc9

On Tue, Apr 15, 2008 at 9:25 AM, Ingo Molnar <mingo@...e.hu> wrote:
>  so it's probably the first few page allocations (setup_cpu_cache())
>  going wrong already - suggesting a some fundamental borkage in SLAB?

I think it's still pointing to the page allocator and/or setting up
the zonelists...

>  note, when i change SLAB to SLUB (and keep the config unchanged
>  otherwise), i get a similar early crash:

...especially considering you have similar crash with SLUB as well.

Now this:

[    0.000999] ------------[ cut here ]------------
[    0.000999] WARNING: at mm/slab.c:1685 cache_alloc_refill+0x2a6/0x4a3()
[    0.000999] Pid: 0, comm: swapper Not tainted 2.6.25-rc9 #924
[    0.000999]  [<c0121b6f>] warn_on_slowpath+0x3c/0x4c
[    0.000999]  [<c0781873>] ? _spin_unlock_irqrestore+0xf/0x13
[    0.000999]  [<c02941ad>] ? delay_tsc+0x2e/0x4e
[    0.000999]  [<c029414d>] ? __delay+0x9/0xb
[    0.000999]  [<c0353db3>] ? serial8250_console_putchar+0x80/0x86
[    0.000999]  [<c0148822>] ? get_page_from_freelist+0x230/0x345
[    0.000999]  [<c0121eb1>] ? __call_console_drivers+0x56/0x63
[    0.000999]  [<c01489bb>] ? __alloc_pages+0x6e/0x2be
[    0.000999]  [<c015bd2e>] cache_alloc_refill+0x2a6/0x4a3
[    0.000999]  [<c015ba3f>] kmem_cache_alloc+0x5b/0xa4

Says that alloc_pages_node() returned NULL early on in the boot.
However, GFP_THISNODE is ruled out as this:

Index: linux/mm/page_alloc.c
===================================================================
--- linux.orig/mm/page_alloc.c
+++ linux/mm/page_alloc.c
@@ -1485,6 +1485,7 @@ restart:
                * Happens if we have an empty zonelist as a result of
                * GFP_THISNODE being used on a memoryless node
                */
+               WARN_ON(1);
               return NULL;
       }

does not trigger. Hmm...
--
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/