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: security-testing tree build failure
Date: Mon, 10 Aug 2009 10:07:49 -0400 [thread overview]
Message-ID: <1249913269.2081.1.camel@dhcp231-106.rdu.redhat.com> (raw)
In-Reply-To: <20090807145932.77bc2c98.sfr@canb.auug.org.au>
On Fri, 2009-08-07 at 14:59 +1000, Stephen Rothwell wrote:
> Hi James,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> kernel/sysctl.c:1321: error: 'mmap_min_addr_handler' undeclared here (not in a function)
> mm/mmap.c: In function 'do_mmap_pgoff':
> mm/mmap.c:935: error: implicit declaration of function 'round_hint_to_min'
>
> Caused by commit a2551df7ec568d87793d2eea4ca744e86318f205
> ("Security/SELinux: seperate lsm specific mmap_min_addr") -
> CONFIG_SECURITY is not set in this build.
>
> I have used the version of the security-testing tree from next-20090806
> for today.
Sorry, I thought I put the definitions outside of the ifdef in
security.h but clearly they aren't. Looks like James's tree has the fix
as of a couple of hours ago, so you should be fix on your next pull from
him.
-Eric
next prev parent reply other threads:[~2009-08-10 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 4:59 Stephen Rothwell
2009-08-10 14:07 ` Eric Paris [this message]
2009-08-10 23:58 ` Stephen Rothwell
2009-09-03 5:51 Stephen Rothwell
2009-09-07 10:38 Stephen Rothwell
2009-09-07 13:40 Stephen Rothwell
2009-09-07 13:43 ` Stephen Rothwell
2009-09-08 0:40 ` Stephen Rothwell
2009-09-08 3:22 ` 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=1249913269.2081.1.camel@dhcp231-106.rdu.redhat.com \
--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
all inboxes | Powered by JetHome®