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
Subject: Re: linux-next: security-testing tree build failure
Date: Fri, 14 Nov 2008 17:42:02 -0500 [thread overview]
Message-ID: <1226702522.3353.85.camel@localhost.localdomain> (raw)
In-Reply-To: <20081114184313.27dbe432.sfr@canb.auug.org.au>
On Fri, 2008-11-14 at 18:43 +1100, Stephen Rothwell wrote:
> Hi James,
>
> On Thu, 13 Nov 2008 18:46:24 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Today's linux-next build (powerpc pseries_defconfig) failed like this:
> >
> > kernel/built-in.o: In function `.__audit_log_bprm_fcaps':
> > (.text+0x63aec): undefined reference to `.get_vfs_caps_from_disk'
> > kernel/built-in.o: In function `.audit_copy_inode':
> > auditsc.c:(.text+0x64594): undefined reference to `.get_vfs_caps_from_disk'
> >
> > get_vfs_caps_from_disk() is protected by
> > CONFIG_SECURITY_FILE_CAPABILITIES but the call sites in kernel/auditsc.c
> > are not.
>
> This error is still there today. I will have to drop the
> security-testing tree on Monday if this is not fixed.
I am aware. James didn't like my first fix for CONFIG_AUDIT but not
CONFIG_SECURITY_FILE_CAPABILITIES so I just sent another one which
should address the concern.
-Eric
next prev parent reply other threads:[~2008-11-14 22:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 7:46 linux-next: security-testing tree build failure Stephen Rothwell
2008-11-14 7:43 ` Stephen Rothwell
2008-11-14 22:42 ` Eric Paris [this message]
2008-11-15 1:56 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
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
2009-09-07 10:38 Stephen Rothwell
2009-09-03 5:51 Stephen Rothwell
2009-08-07 4:59 Stephen Rothwell
2009-08-10 14:07 ` Eric Paris
2009-08-10 23:58 ` Stephen Rothwell
2009-02-06 7:28 Stephen Rothwell
2009-02-06 8:14 ` James Morris
2008-11-12 5:05 Stephen Rothwell
2008-11-12 10:56 ` James Morris
2008-11-12 14:05 ` Eric Paris
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=1226702522.3353.85.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=jmorris@namei.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