summaryrefslogtreecommitdiffstats
path: root/kernel/seccomp.c
diff options
context:
space:
mode:
authorDaniel Borkmann <daniel@iogearbox.net>2015-05-06 16:12:29 +0200
committerDavid S. Miller <davem@davemloft.net>2015-05-09 17:35:05 -0400
commit658da9379d0e1aa1e3e40c9b795357ada818b1c8 (patch)
treed867298c84e4ba073c195b1b8009c2a0d4a243da /kernel/seccomp.c
parentd9e12f42e58da475379b9080708b94f2095904af (diff)
downloadop-kernel-dev-658da9379d0e1aa1e3e40c9b795357ada818b1c8.zip
op-kernel-dev-658da9379d0e1aa1e3e40c9b795357ada818b1c8.tar.gz
net: filter: add __GFP_NOWARN flag for larger kmem allocs
When seccomp BPF was added, it was discussed to add __GFP_NOWARN flag for their configuration path as f.e. up to 32K allocations are more prone to fail under stress. As we're going to reuse BPF API, add __GFP_NOWARN flags where larger kmalloc() and friends allocations could fail. It doesn't make much sense to pass around __GFP_NOWARN everywhere as an extra argument only for seccomp while we just as well could run into similar issues for socket filters, where it's not desired to have a user application throw a WARN() due to allocation failure. Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Cc: Nicolas Schichan <nschichan@freebox.fr> Cc: Alexei Starovoitov <ast@plumgrid.com> Cc: Kees Cook <keescook@chromium.org> Acked-by: Alexei Starovoitov <ast@plumgrid.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'kernel/seccomp.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud