linux-kernel - [PATCH]: x86-64 system crashes when no memory populating Node 0

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

Date:	Fri, 22 Dec 2006 12:47:13 -0500
From:	James Puthukattukaran <James.Puthukattukaran@....com>
To:	linux-kernel@...r.kernel.org
Subject: [PATCH]: x86-64 system crashes when no memory populating Node 0

I have a 4 socket AMD Operton system. The 2.6.18 kernel I have crashes 
when there is no memory in node0.

--James


diff -uNr linux-2.6.18-orig/arch/x86_64/kernel/aperture.c 
linux-2.6.18-new/arch/x86_64/kernel/aperture.c
--- linux-2.6.18-orig/arch/x86_64/kernel/aperture.c     2006-09-19 
23:42:06.000000000 -0400
+++ linux-2.6.18-new/arch/x86_64/kernel/aperture.c      2006-12-20 
19:43:42.000000000 -0500
@@ -38,7 +38,6 @@

 static u32 __init allocate_aperture(void)
 {
-       pg_data_t *nd0 = NODE_DATA(0);
        u32 aper_size;
        void *p;

@@ -52,12 +51,13 @@
         * Unfortunately we cannot move it up because that would make the
         * IOMMU useless.
         */
-       p = __alloc_bootmem_node(nd0, aper_size, aper_size, 0);
+
+       p = __alloc_bootmem(aper_size, aper_size, 0);
        if (!p || __pa(p)+aper_size > 0xffffffff) {
                printk("Cannot allocate aperture memory hole (%p,%uK)\n",
                       p, aper_size>>10);
                if (p)
-                       free_bootmem_node(nd0, __pa(p), aper_size);
+                       free_bootmem(__pa(p), aper_size);
                return 0;
        }
        printk("Mapping aperture over %d KB of RAM @ %lx\n",

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