diff options
author | 2023-12-12 16:26:59 -0700 | |
---|---|---|
committer | 2023-12-20 13:46:19 -0800 | |
commit | b2325bf860faa2f304a7e188f00cf9f7dc9b5ee8 (patch) | |
tree | cc692a83b0b88c1032a68c0a7d6ed1bae04c6ad6 /mm/filemap.c | |
parent | kexec: select CRYPTO from KEXEC_FILE instead of depending on it (diff) | |
download | linux-b2325bf860faa2f304a7e188f00cf9f7dc9b5ee8.tar.gz linux-b2325bf860faa2f304a7e188f00cf9f7dc9b5ee8.tar.bz2 linux-b2325bf860faa2f304a7e188f00cf9f7dc9b5ee8.zip |
kunit: kasan_test: disable fortify string checker on kmalloc_oob_memset
Similar to commit 09c6304e38e4 ("kasan: test: fix compatibility with
FORTIFY_SOURCE") the kernel is panicing in kmalloc_oob_memset_*.
This is due to the `ptr` not being hidden from the optimizer which would
disable the runtime fortify string checker.
kernel BUG at lib/string_helpers.c:1048!
Call Trace:
[<00000000272502e2>] fortify_panic+0x2a/0x30
([<00000000272502de>] fortify_panic+0x26/0x30)
[<001bffff817045c4>] kmalloc_oob_memset_2+0x22c/0x230 [kasan_test]
Hide the `ptr` variable from the optimizer to fix the kernel panic. Also
define a memset_size variable and hide that as well. This cleans up the
code and follows the same convention as other tests.
[npache@redhat.com: address review comments from Andrey]
Link: https://lkml.kernel.org/r/20231214164423.6202-1-npache@redhat.com
Link: https://lkml.kernel.org/r/20231212232659.18839-1-npache@redhat.com
Signed-off-by: Nico Pache <npache@redhat.com>
Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
Cc: Alexander Potapenko <glider@google.com>
Cc: Andrey Konovalov <andreyknvl@gmail.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm/filemap.c')
0 files changed, 0 insertions, 0 deletions