Messages in this thread Patch in this message | | | From | Norbert Manthey <> | Subject | [less-CONFIG_NET 6/7] seccomp: drop CONFIG_NET | Date | Wed, 6 Jun 2018 15:53:25 +0200 |
| |
With the goal of dropping CONFIG_NET, we have to drop the dependency in the configuration management. Since SECCOMP_FILTER also requires BPF functionality, which is usually activated by CONFIG_NET, imply BPF from SECCOMP_FILTER directly.
In case both CONFIG_NET and CONFIG_SECCOMP_FILTER are activated, BPF will be activated as well, so this additional dependency does not destroy original builds.
Signed-off-by: Norbert Manthey <nmanthey@amazon.de> --- arch/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/Kconfig b/arch/Kconfig index 75dd23a..c7108fd 100644 --- a/arch/Kconfig +++ b/arch/Kconfig @@ -393,7 +393,8 @@ config HAVE_ARCH_SECCOMP_FILTER config SECCOMP_FILTER def_bool y - depends on HAVE_ARCH_SECCOMP_FILTER && SECCOMP && NET + depends on HAVE_ARCH_SECCOMP_FILTER && SECCOMP + select BPF help Enable tasks to build secure computing environments defined in terms of Berkeley Packet Filter programs which implement -- 2.7.4 Amazon Development Center Germany GmbH Berlin - Dresden - Aachen main office: Krausenstr. 38, 10117 Berlin Geschaeftsfuehrer: Dr. Ralf Herbrich, Christian Schlaeger Ust-ID: DE289237879 Eingetragen am Amtsgericht Charlottenburg HRB 149173 B
| |