linux-kernel - Re: 2.6.18-rc4-mm2: m68k nsproxy compile breakage

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]

Message-ID: <20060821165158.GK11651@stusta.de>
Date:	Mon, 21 Aug 2006 18:51:58 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	"Serge E. Hallyn" <serue@...ibm.com>
Cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.18-rc4-mm2: m68k nsproxy compile breakage

On Mon, Aug 21, 2006 at 09:46:49AM -0500, Serge E. Hallyn wrote:
> Quoting Adrian Bunk (bunk@...sta.de):
> > namespaces-utsname-implement-utsname-namespaces.patch causes the 
> > following compile error on m68k:
> > 
> > <--  snip  -->
> > 
> > ...
> >   LD      .tmp_vmlinux1
> > arch/m68k/kernel/built-in.o: In function `sys_call_table':
> > (.data+0x91c): undefined reference to `init_nsproxy'
> > 
> > <--  snip  -->
> > 
> > Is there a reason why struct init_nsproxy can't reside in 
> > kernel/nsproxy.c?
> 
> Apparently not.  The following patch compiles and boots fine on s390.
>...

Thanks, I can confirm it fixes this compile error on m68k.

cu
Adrian

-- 

    Gentoo kernels are 42 times more popular than SUSE kernels among
    KLive users  (a service by SUSE contractor Andrea Arcangeli that
    gathers data about kernels from many users worldwide).

       There are three kinds of lies: Lies, Damn Lies, and Statistics.
                                                    Benjamin Disraeli

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