From: Shea Levy <shea@shealevy.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Serge Hallyn <serge.hallyn@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 3.8.9 Build Failure in user_namespace.c
Date: Thu, 02 May 2013 00:31:39 -0400 [thread overview]
Message-ID: <5181EC2B.2030405@shealevy.com> (raw)
In-Reply-To: <20130429205628.GA20607@austin.hallyn.com>
On 4/29/13 4:56 PM, Serge E. Hallyn wrote:
> Quoting shea@shealevy.com (shea@shealevy.com):
>> Hi All,
>>
>> I just hit the following error trying to build 3.8.9:
>>
>> /nix/store/vkvwpn6f7iff6zqrq2d9z2a1945pcsza-linux-3.8.9-source/kernel/user_namespace.c:
>> In function 'map_write':
>> /nix/store/vkvwpn6f7iff6zqrq2d9z2a1945pcsza-linux-3.8.9-source/kernel/user_namespace.c:582:2:
>> error: implicit declaration of function 'file_ns_capable'
>> [-Werror=implicit-function-declaration]
>> cc1: some warnings being treated as errors
>>
>> Below is my .config, below that the build log.
> I'm looking at 3.9. file_ns_capable() is declared in capability.h, which gets
> included into user_namespace.c through cred.h. I did also try building with
> CONFIG_SECURITY=n and CONFIG_USER_NS=y as you have it, but build succeeded,
> as I would expect given how it is included.
It turned out to be a commit Greg missed in 3.8.9, it was fixed in 3.8.10.
> Do you have any custom patches applied by chance?
>
> -serge
prev parent reply other threads:[~2013-05-02 4:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 17:38 Linux 3.8.9 Build Failure in user_namespace.c shea
2013-04-29 20:56 ` Serge E. Hallyn
2013-05-02 4:31 ` Shea Levy [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=5181EC2B.2030405@shealevy.com \
--to=shea@shealevy.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serge.hallyn@canonical.com \
--cc=serge@hallyn.com \
/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