From: ebiederm@xmission.com (Eric W. Biederman)
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (namespace tree related)
Date: Thu, 12 May 2011 15:27:27 -0700 [thread overview]
Message-ID: <m1zkmrlflc.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20110512135113.93c1b671.sfr@canb.auug.org.au> (Stephen Rothwell's message of "Thu, 12 May 2011 13:51:13 +1000")
Stephen Rothwell <sfr@canb.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
prev parent reply other threads:[~2011-05-12 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 3:51 linux-next: build failure after merge of the final tree (namespace tree related) Stephen Rothwell
2011-05-12 22:27 ` Eric W. Biederman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1zkmrlflc.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox