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] [day] [month] [year] [list]
Date:	Tue, 21 Nov 2006 13:45:10 +0100
From:	Karsten Wiese <fzu@...gehoertderstaat.de>
To:	Marcus Hartig <m.f.h@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.19-rc6-rt5

Am Dienstag, 21. November 2006 13:01 schrieb Marcus Hartig:
> HI!
> 
> rt4 runs fine. But while compiling 2.6.19-rc6-rt5 I get this error:
> 
> CC      mm/page_alloc.o
> mm/page_alloc.c: In function 'page_alloc_init':
> mm/page_alloc.c:2793: error: 'page_alloc_cpu_notify' undeclared (first use 
> in this function)
> mm/page_alloc.c:2793: error: (Each undeclared identifier is reported only once
> mm/page_alloc.c:2793: error: for each function it appears in.)
> make[1]: *** [mm/page_alloc.o] Error 1
> make: *** [mm] Error 2

Ingo posted a fix in another thread.
The (whitespace damaged, handapply!) excerpt of that fix below made
i386 compile here.

      Karsten

Index: linux/mm/page_alloc.c
===================================================================
--- linux.orig/mm/page_alloc.c
+++ linux/mm/page_alloc.c
@@ -2768,7 +2768,6 @@ void __init free_area_init(unsigned long
                        __pa(PAGE_OFFSET) >> PAGE_SHIFT, NULL);
 }
 
-#ifdef CONFIG_HOTPLUG_CPU
 static int page_alloc_cpu_notify(struct notifier_block *self,
                                 unsigned long action, void *hcpu)
 {
@@ -2786,7 +2785,6 @@ static int page_alloc_cpu_notify(struct 
        }
        return NOTIFY_OK;
 }
-#endif /* CONFIG_HOTPLUG_CPU */
 
 void __init page_alloc_init(void)
 {
-
-
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