linux-kernel - Re: v2.6.35-git2 SELinux build failure

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]

Date:	Mon, 09 Aug 2010 13:21:49 -0400
From:	Eric Paris <eparis@...hat.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	James Morris <jmorris@...ei.org>,
	Eric Paris <eparis@...isplace.org>,
	linux-kernel@...r.kernel.org
Subject: Re: v2.6.35-git2 SELinux build failure

On Mon, 2010-08-09 at 12:21 -0400, Theodore Ts'o wrote:
> Commit b782e0a6, introduced in v2.6.35-git2, uses FILE__AUDIT_ACCESS
> without actually defining it:
> 
> security/selinux/hooks.c:2644: error: ‘FILE__AUDIT_ACCESS’ undeclared
> (first use in this function)
> 
> I first noticed this in 2.6.35-git6, and it is still broken in
> 2.6.35-git7.  I'm not sure how SELinux got turned on in my config, but
> I'm not using it, so I'm going to fix it by turning off SELinux.  I
> thought I would mention it first, though.

You must be using O=$builddir ??

Lets start by saying that the security/selinux/av_permissions.h file is
automatically generated by scripts/selinux/mdp/genheaders.  On you
system I'll bet the problem is that
$srcdir/security/selinux/av_permissions.h exists and doesn't define
FILE__AUDIT_ACCESS.  You will also likely see that
$builddir/security/selinux/av_permission.h exists and does define
FILE__AUDIT_ACCESS.  The $srcdir version should have been cleaned up
before you were allowed to build with O= but wasn't.

This was fixed in a7a387cc596278af1516c534b50cc0bee171129d

See: http://marc.info/?l=selinux&m=128112456326419&w=2

Run make clean.  Try again.

-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/