aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/stackdepot.py
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2024-04-29 12:43:41 -0700
committerKees Cook <keescook@chromium.org>2024-04-30 10:34:30 -0700
commit26f812ba75890c48644a31e3cfe3dd9762138968 (patch)
tree20dc3e07c3d14725fdc4f1e1f146e6d4978c08db /scripts/gdb/linux/stackdepot.py
parent091f79e8de44736a1e677701d67334bba5b749e3 (diff)
kunit/fortify: Add memcpy() tests
Add fortify tests for memcpy() and memmove(). This can use a similar method to the fortify_panic() replacement, only we can do it for what was the WARN_ONCE(), which can be redefined. Since this is primarily testing the fortify behaviors of the memcpy() and memmove() defenses, the tests for memcpy() and memmove() are identical. Link: https://lore.kernel.org/r/20240429194342.2421639-3-keescook@chromium.org Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'scripts/gdb/linux/stackdepot.py')
0 files changed, 0 insertions, 0 deletions