From: ebiederm@xmission.com (Eric W. Biederman)
To: kernel-janitors@vger.kernel.org
Subject: Re: [userns:for-next 10/23] ERROR: "free_pid_ns" [net/ipv6/ipv6.ko] undefined!
Date: Wed, 15 Aug 2012 06:34:58 +0000 [thread overview]
Message-ID: <87has4fyst.fsf@xmission.com> (raw)
In-Reply-To: <877gt0hgak.fsf@xmission.com>
Fengguang Wu <fengguang.wu@intel.com> writes:
> On Tue, Aug 14, 2012 at 10:31:47PM -0700, Eric W. Biederman wrote:
>> Fengguang Wu <fengguang.wu@intel.com> writes:
>>
>> > Hi Eric,
>> >
>> > FYI, kernel build failed on
>> >
>> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-next
>> > head: 0625c883bc4b3eba6f93f268cf67b5664244c0fe
>> > commit: 4f82f45730c68fdaf9b0472495a965188404866e [10/23] net ip6 flowlabel: Make owner a union of struct pid * and kuid_t
>> > config: x86_64-allmodconfig (attached as .config)
>> >
>> > Build errors:
>> >
>> > ERROR: "free_pid_ns" [net/ipv6/ipv6.ko] undefined!
>>
>> Yes, and the next patch fixes that.
>>
>> My apologies to git bisect users that the support for modular ipv6 is
>> not perfect.
>
> Fine for me - I normally build-in everything ;)
I guess that was my long winded way of saying once patches hit my
for-next branch I have no intention of rebasing to fix problems.
Now if you automated checker had gone to the base of my
userns-always-map-user-v46 branch where these patches were staged and
complained then I probably would have fixed the problem.
It looks like your checker limits itself to only the last 99 patches in
a branch and my branch has about 130 or so.
Eric
next prev parent reply other threads:[~2012-08-15 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 5:31 [userns:for-next 10/23] ERROR: "free_pid_ns" [net/ipv6/ipv6.ko] undefined! Eric W. Biederman
2012-08-15 5:35 ` Fengguang Wu
2012-08-15 6:34 ` Eric W. Biederman [this message]
2012-08-15 7:07 ` Fengguang Wu
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=87has4fyst.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=kernel-janitors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.