diff options
author | Christophe Leroy <christophe.leroy@csgroup.eu> | 2024-09-07 17:40:42 +0200 |
---|---|---|
committer | Andrew Morton <akpm@linux-foundation.org> | 2024-09-17 01:07:00 -0700 |
commit | 82ce8e2f31a1eb05b1527c3d807bea40031df913 (patch) | |
tree | f0a6bdc269f18d71876da9092cbb7dec41272ed3 /mm | |
parent | 659c55ef981bb63355a65ffc3b3b5cad562b806a (diff) | |
download | linux-stable-82ce8e2f31a1eb05b1527c3d807bea40031df913.tar.gz linux-stable-82ce8e2f31a1eb05b1527c3d807bea40031df913.tar.bz2 linux-stable-82ce8e2f31a1eb05b1527c3d807bea40031df913.zip |
set_memory: add __must_check to generic stubs
Following query shows that architectures that don't provide
asm/set_memory.h don't use set_memory_...() functions.
$ git grep set_memory_ alpha arc csky hexagon loongarch m68k microblaze mips nios2 openrisc parisc sh sparc um xtensa
Following query shows that all core users of set_memory_...()
functions always take returned value into account:
$ git grep -w -e set_memory_ro -e set_memory_rw -e set_memory_x -e set_memory_nx -e set_memory_rox `find . -maxdepth 1 -type d | grep -v arch | grep /`
set_memory_...() functions can fail, leaving the memory attributes
unchanged. Make sure all callers check the returned code.
Link: https://github.com/KSPP/linux/issues/7
Link: https://lkml.kernel.org/r/6a89ffc69666de84721216947c6b6c7dcca39d7d.1725723347.git.christophe.leroy@csgroup.eu
Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Kees Cook <kees@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions