linux-kernel - Re: selinux build error - ‘FILE__AUDIT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1282101359.11858.34.camel@minggr.sh.intel.com>
Date:	Wed, 18 Aug 2010 11:15:59 +0800
From:	Lin Ming <ming.m.lin@...el.com>
To:	Eric Paris <eparis@...hat.com>
Cc:	"Stephen D. Smalley" <sds@...ho.nsa.gov>,
	James Morris <jmorris@...ei.org>, Ingo Molnar <mingo@...e.hu>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: selinux build error -
 ‘FILE__AUDIT_ACCESS’ undeclared

On Tue, 2010-08-17 at 19:37 +0800, Eric Paris wrote:
> On Tue, 2010-08-17 at 16:15 +0800, Lin Ming wrote:
> > Current -tip(a3b97ee) tree build error.
> > My config attached.
> > 
> > linux-2.6/security/selinux/hooks.c: In function ‘selinux_inode_permission’:
> > linux-2.6/security/selinux/hooks.c:2647:38: error: ‘FILE__AUDIT_ACCESS’ undeclared (first use in this function)
> > 
> > It was introduced by below commit.
> > 
> > commit b782e0a68d17894d9a618ffea55b33639faa6bb4
> > Author: Eric Paris <eparis@...hat.com>
> > Date:   Fri Jul 23 11:44:03 2010 -0400
> > 
> >     SELinux: special dontaudit for access checks
> > 
> > Lin Ming
> 
> did you build with O= ?

Yes.

> 
> Fixed in a7a387cc596278af1516c534b50cc0bee171129d but you have to run
> make clean.  If you want to fix it up by hand run:
> 
> find . -name av_pernmissions.h | xargs rm
> 
> Your builds will work find after that.

Works now.

Thanks.

> 
> -Eric
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/