Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Marco Elver 5f44e5ced3 UPSTREAM: kfence: report sensitive information based on no_hash_pointers ... We cannot rely on CONFIG_DEBUG_KERNEL to decide if we're running a "debug kernel" where we can safely show potentially sensitive information in the kernel log. Instead, simply rely on the newly introduced "no_hash_pointers" to print unhashed kernel pointers, as well as decide if our reports can include other potentially sensitive information such as registers and corrupted bytes. Link: https://lkml.kernel.org/r/20210223082043.1972742-1-elver@google.com Signed-off-by: Marco Elver <elver@google.com> Cc: Timur Tabi <timur@kernel.org> Cc: Alexander Potapenko <glider@google.com> Cc: Dmitry Vyukov <dvyukov@google.com> Cc: Andrey Konovalov <andreyknvl@google.com> Cc: Jann Horn <jannh@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Bug: 177201466 Bug: 180086542 (cherry picked from commit 35beccf0926d42ee0d56e41979ec8cdf814c4769) Signed-off-by: Alexander Potapenko <glider@google.com> Change-Id: Ie76403ee1b902742a6ac300ad13bd117a02f93f1		2026-05-07 17:24:07 +03:00
..
coccinelle.rst
gcov.rst
gdb-kernel-debugging.rst
index.rst	BACKPORT: kfence, Documentation: add KFENCE documentation	2026-05-07 17:24:04 +03:00
kasan.rst
kcov.rst
kfence.rst	UPSTREAM: kfence: report sensitive information based on no_hash_pointers	2026-05-07 17:24:07 +03:00
kgdb.rst
kmemleak.rst
kselftest.rst
sparse.rst
ubsan.rst