diff options
| author | Laura Abbott <labbott@fedoraproject.org> | 2016-02-26 03:36:42 +0300 |
|---|---|---|
| committer | Kees Cook <keescook@chromium.org> | 2016-03-02 01:29:13 +0300 |
| commit | bc0b8cc6cb26a209fa1679d5c063b47bc0afe964 (patch) | |
| tree | 6edbd0fa562a4505d21906d1db3feae7fea16841 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | ea861d73a9aa97a5e0c7cef6a26ce01786e0c58d (diff) | |
| download | linux-bc0b8cc6cb26a209fa1679d5c063b47bc0afe964.tar.xz | |
lkdtm: Add READ_AFTER_FREE test
In a similar manner to WRITE_AFTER_FREE, add a READ_AFTER_FREE
test to test free poisoning features. Sample output when
no sanitization is present:
# echo READ_AFTER_FREE > /sys/kernel/debug/provoke-crash/DIRECT
[ 17.542473] lkdtm: Performing direct entry READ_AFTER_FREE
[ 17.543866] lkdtm: Value in memory before free: 12345678
[ 17.545212] lkdtm: Attempting bad read from freed memory
[ 17.546542] lkdtm: Memory was not poisoned
with slub_debug=P:
# echo READ_AFTER_FREE > /sys/kernel/debug/provoke-crash/DIRECT
[ 22.415531] lkdtm: Performing direct entry READ_AFTER_FREE
[ 22.416366] lkdtm: Value in memory before free: 12345678
[ 22.417137] lkdtm: Attempting bad read from freed memory
[ 22.417897] lkdtm: Memory correctly poisoned, calling BUG
Signed-off-by: Laura Abbott <labbott@fedoraproject.org>
Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions