summaryrefslogtreecommitdiff
path: root/security
diff options
context:
space:
mode:
authorVlastimil Babka <vbabka@suse.cz>2023-05-23 09:26:35 +0200
committerVlastimil Babka <vbabka@suse.cz>2023-05-24 15:38:17 +0200
commitd2e527f0d8d1124b1fab93e2e7b2c6a114c0e5a2 (patch)
treedcb50532d07591052402090550cde585d8b055df /security
parent8040cbf5e1da2fe86558239b92927a947c79ecd6 (diff)
mm/slab: remove HAVE_HARDENED_USERCOPY_ALLOCATOR
With SLOB removed, both remaining allocators support hardened usercopy, so remove the config and associated #ifdef. Signed-off-by: Vlastimil Babka <vbabka@suse.cz> Reviewed-by: David Hildenbrand <david@redhat.com> Reviewed-by: Lorenzo Stoakes <lstoakes@gmail.com> Reviewed-by: Kees Cook <keescook@chromium.org> Acked-by: David Rientjes <rientjes@google.com> Acked-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>
Diffstat (limited to 'security')
-rw-r--r--security/Kconfig8
1 files changed, 0 insertions, 8 deletions
diff --git a/security/Kconfig b/security/Kconfig
index 97abeb9b9a19..52c9af08ad35 100644
--- a/security/Kconfig
+++ b/security/Kconfig
@@ -127,16 +127,8 @@ config LSM_MMAP_MIN_ADDR
this low address space will need the permission specific to the
systems running LSM.
-config HAVE_HARDENED_USERCOPY_ALLOCATOR
- bool
- help
- The heap allocator implements __check_heap_object() for
- validating memory ranges against heap object sizes in
- support of CONFIG_HARDENED_USERCOPY.
-
config HARDENED_USERCOPY
bool "Harden memory copies between kernel and userspace"
- depends on HAVE_HARDENED_USERCOPY_ALLOCATOR
imply STRICT_DEVMEM
help
This option checks for obviously wrong memory regions when