From: James Morris <jmorris@namei.org>
To: Will Drewry <wad@chromium.org>
Cc: james@namei.org, paul.gortmaker@windriver.com, eparis@redhat.com,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
keescook@chromium.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] samples/seccomp: fix dependencies on arch macros
Date: Thu, 19 Apr 2012 13:44:44 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.2.02.1204191344290.563@tundra.namei.org> (raw)
In-Reply-To: <1334796625-26830-1-git-send-email-wad@chromium.org>
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@windriver.com>
> Suggested-by: Kees Cook <keescook@chromium.org>
> Signed-off-by: Will Drewry <wad@chromium.org>
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2012-04-19 3:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 0:50 [PATCH] samples/seccomp: fix dependencies on arch macros Will Drewry
2012-04-19 3:44 ` James Morris [this message]
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=alpine.LRH.2.02.1204191344290.563@tundra.namei.org \
--to=jmorris@namei.org \
--cc=eparis@redhat.com \
--cc=james@namei.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=wad@chromium.org \
/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