diff options
| author | Olof Johansson <olof@lixom.net> | 2016-07-05 23:53:19 -0700 |
|---|---|---|
| committer | Kees Cook <keescook@chromium.org> | 2016-07-07 10:58:03 -0700 |
| commit | f6041c1d8a0825e41219a0443d365318d238d7b3 (patch) | |
| tree | a46722209d07b7de7111ac77c384e3738b36771a /fs/hpfs | |
| parent | d011a4d861ce583466a8ae72a0c8e7f51c8cba4e (diff) | |
| download | linux-f6041c1d8a0825e41219a0443d365318d238d7b3.tar.gz linux-f6041c1d8a0825e41219a0443d365318d238d7b3.tar.bz2 linux-f6041c1d8a0825e41219a0443d365318d238d7b3.zip | |
samples/seccomp: Add standalone config option
Add a separate Kconfig option for SAMPLES_SECCOMP.
Main reason for this is that, just like other samples, it's forced to
be a module.
Without this, since the sample is a target only controlled by
CONFIG_SECCOMP_FILTER, the samples will be built before include files are
put in place properly. For example, from an arm64 allmodconfig built with
"make -sk -j 32" (without specific target), the following happens:
samples/seccomp/bpf-fancy.c:13:27: fatal error: linux/seccomp.h: No such file or directory
samples/seccomp/bpf-helper.h:20:50: fatal error: linux/seccomp.h: No such file or directory
samples/seccomp/dropper.c:20:27: fatal error: linux/seccomp.h: No such file or directory
samples/seccomp/bpf-direct.c:21:27: fatal error: linux/seccomp.h: No such file or directory
So, just stick to the same format as other samples.
Signed-off-by: Olof Johansson <olof@lixom.net>
Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'fs/hpfs')
0 files changed, 0 insertions, 0 deletions