diff options
| author | Kees Cook <keescook@chromium.org> | 2022-05-10 19:29:36 +0200 |
|---|---|---|
| committer | Kees Cook <keescook@chromium.org> | 2022-05-10 19:40:26 +0200 |
| commit | 1ff297584fad2eef390f212b860e0fbb7363e0e8 (patch) | |
| tree | c3c7aa0bdbb4ee93e782f293fd316575d8138a46 /scripts/parse-maintainers.pl | |
| parent | lkdtm/stackleak: fix CONFIG_GCC_PLUGIN_STACKLEAK=n (diff) | |
| download | linux-1ff297584fad2eef390f212b860e0fbb7363e0e8.tar.xz linux-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/1652173338.7bltwybi0c.astroid@bobo.none
Cc: Nicholas Piggin <npiggin@gmail.com>
Cc: Xiu Jianfeng <xiujianfeng@huawei.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'scripts/parse-maintainers.pl')
0 files changed, 0 insertions, 0 deletions