linux-kernel - Re: 2.6.18-rc4-mm3

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:	Tue, 29 Aug 2006 17:18:58 +0200
From:	Cedric Le Goater <clg@...ibm.com>
To:	Haavard Skinnemoen <hskinnemoen@...el.com>
CC:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	"Serge E. Hallyn" <serue@...ibm.com>
Subject: Re: 2.6.18-rc4-mm3

Haavard Skinnemoen wrote:
> On Sat, 26 Aug 2006 16:09:22 -0700
> Andrew Morton <akpm@...l.org> wrote:
> 
>> +namespaces-add-nsproxy-move-init_nsproxy-into-kernel-nsproxyc.patch
> 
> This causes a multiple definition of init_nsproxy on AVR32. Reverting
> namespaces-add-nsproxy-avr32-fix.patch fixes it.

Could you try this ?

thanks,

C.


Signed-off-by: Cedric Le Goater <clg@...ibm.com>

---
 arch/avr32/kernel/init_task.c |    2 --
 1 file changed, 2 deletions(-)

Index: 2.6.18-rc4-mm3/arch/avr32/kernel/init_task.c
===================================================================
--- 2.6.18-rc4-mm3.orig/arch/avr32/kernel/init_task.c
+++ 2.6.18-rc4-mm3/arch/avr32/kernel/init_task.c
@@ -10,7 +10,6 @@
 #include <linux/sched.h>
 #include <linux/init_task.h>
 #include <linux/mqueue.h>
-#include <linux/nsproxy.h>

 #include <asm/pgtable.h>

@@ -19,7 +18,6 @@ static struct files_struct init_files =
 static struct signal_struct init_signals = INIT_SIGNALS(init_signals);
 static struct sighand_struct init_sighand = INIT_SIGHAND(init_sighand);
 struct mm_struct init_mm = INIT_MM(init_mm);
-struct nsproxy init_nsproxy = INIT_NSPROXY(init_nsproxy);

 EXPORT_SYMBOL(init_mm);

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