From: Eric Paris <eparis@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: James Morris <jmorris@namei.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (security-testing tree related)
Date: Wed, 20 Oct 2010 07:46:02 -0400 [thread overview]
Message-ID: <1287575162.2530.285.camel@localhost.localdomain> (raw)
In-Reply-To: <20101020161024.af794b4a.sfr@canb.auug.org.au>
On Wed, 2010-10-20 at 16:10 +1100, Stephen Rothwell wrote:
> Hi James,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> security/selinux/ss/services.c: In function 'security_read_policy':
> security/selinux/ss/services.c:3172: error: implicit declaration of function 'vmalloc_user'
> security/selinux/ss/services.c:3172: warning: assignment makes pointer from integer without a cast
>
> Caused by commit ed167abda544bb7f8cf09dc3d3608c79e1cfb25f ("SELinux:
> allow userspace to read policy back out of the kernel") and
> bb17427490e1e295f3c0550c308684bd952a585d ("selinux: implement mmap
> on /selinux/policy").
>
> Please see Rule 1 (in Documentation/SubmitChecklist).
>
> I applied the following patch for today:
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed, 20 Oct 2010 16:08:00 +1100
> Subject: [PATCH] selinux: include vmalloc.h for vmalloc_user
Huh, not sure why it builds cleanly here. I'm applying my patch series
on top of linux-next from the 18th. In any case this looks correct.
Acked-by: Eric Paris <eparis@redhat.com>
>
> ---
> security/selinux/ss/services.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/security/selinux/ss/services.c b/security/selinux/ss/services.c
> index 3a1739b..223c1ff 100644
> --- a/security/selinux/ss/services.c
> +++ b/security/selinux/ss/services.c
> @@ -51,6 +51,7 @@
> #include <linux/mutex.h>
> #include <linux/selinux.h>
> #include <linux/flex_array.h>
> +#include <linux/vmalloc.h>
> #include <net/netlabel.h>
>
> #include "flask.h"
> --
> 1.7.1
>
next prev parent reply other threads:[~2010-10-20 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 5:10 linux-next: build failure after merge of the final tree (security-testing tree related) Stephen Rothwell
2010-10-20 11:46 ` Eric Paris [this message]
2010-10-20 22:28 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2010-11-29 2:25 Stephen Rothwell
2010-11-29 2:57 ` Stephen Rothwell
2011-07-16 14:05 Stephen Rothwell
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=1287575162.2530.285.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=jmorris@namei.org \
--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;
as well as URLs for NNTP newsgroup(s).