diff options
| author | Kees Cook <[email protected]> | 2022-05-10 17:29:36 +0000 |
|---|---|---|
| committer | Kees Cook <[email protected]> | 2022-05-10 17:40:26 +0000 |
| commit | 1ff297584fad2eef390f212b860e0fbb7363e0e8 (patch) | |
| tree | c3c7aa0bdbb4ee93e782f293fd316575d8138a46 /scripts/gcc-plugins/structleak_plugin.c | |
| parent | lkdtm/stackleak: fix CONFIG_GCC_PLUGIN_STACKLEAK=n (diff) | |
| download | kernel-1ff297584fad2eef390f212b860e0fbb7363e0e8.tar.gz kernel-1ff297584fad2eef390f212b860e0fbb7363e0e8.zip | |
randomize_kstack: Improve docs on requirements/rationale
There were some recent questions about where and why to use the
random_kstack routines when applying them to new architectures[1].
Update the header comments to reflect the design choices for the
routines.
[1] https://lore.kernel.org/lkml/[email protected]
Cc: Nicholas Piggin <[email protected]>
Cc: Xiu Jianfeng <[email protected]>
Signed-off-by: Kees Cook <[email protected]>
Diffstat (limited to 'scripts/gcc-plugins/structleak_plugin.c')
0 files changed, 0 insertions, 0 deletions