linux-kernel - Re: [PATCH] samples/seccomp: fix dependencies on arch macros

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:	Thu, 19 Apr 2012 13:44:44 +1000 (EST)
From:	James Morris <jmorris@...ei.org>
To:	Will Drewry <wad@...omium.org>
cc:	james@...ei.org, paul.gortmaker@...driver.com, eparis@...hat.com,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	keescook@...omium.org, linux-security-module@...r.kernel.org
Subject: Re: [PATCH] samples/seccomp: fix dependencies on arch macros

On Wed, 18 Apr 2012, Will Drewry wrote:

> This change fixes the compilation error triggered here for
> i386 allmodconfig in linux-next:
>   http://kisskb.ellerman.id.au/kisskb/buildresult/6123842/
> 
> Logic attempting to predict the host architecture has been
> removed from the Makefile.  Instead, the bpf-direct sample
> should now compile on any architecture, but if the architecture
> is not supported, it will compile a minimal main() function.
> 
> This change also ensures the samples are not compiled when
> there is no seccomp filter support.
> 
> (Note, I wasn't able to reproduce the error locally, but
>  the existing approach was clearly flawed.  This tweak
>  should resolve your issue and avoid other future weirdness.)
> 
> Reported-by: Paul Gortmaker <paul.gortmaker@...driver.com>
> Suggested-by: Kees Cook <keescook@...omium.org>
> Signed-off-by: Will Drewry <wad@...omium.org>

Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next


-- 
James Morris
<jmorris@...ei.org>
--
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/