linux-kernel - Re: linux-next: build failure after merge of the final tree (namespace tree related)

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]

Message-ID: <m1zkmrlflc.fsf@fess.ebiederm.org>
Date:	Thu, 12 May 2011 15:27:27 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (namespace tree related)

Stephen Rothwell <sfr@...b.auug.org.au> writes:

> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> ppc44x_defconfig) failed like this:
>
> net/built-in.o: In function `get_net_ns_by_fd':
> (.text+0x11976): undefined reference to `netns_operations'
> net/built-in.o: In function `get_net_ns_by_fd':
> (.text+0x1197a): undefined reference to `netns_operations'
>
> netns_operations is only available if CONFIG_NET_NS is set ...
>
> Caused by commit f063052947f7 ("net: Allow setting the network namespace
> by fd").
>
> I applied the patch below for today.

How embarrassing.  I should have caught this one myself.

I have applied your patch.  

At some point I need to see what the impact of removing the various
CONFIG_XXX_NS defines is and get rid of them.  Their original purpose
was only to let administrators avoid buggy code, but most of the
namespaces are well beyond where that now and it seems those
CONFIG_XXX_NS defines are just causing trouble.  But not for 2.6.40.

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