Re: [PATCH mm] kfence: make reporting sensitive information configurable

2021-02-09 Thread Marco Elver
On Tue, 9 Feb 2021 at 19:06, Vlastimil Babka wrote: > On 2/9/21 4:13 PM, Marco Elver wrote: > > 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. > > > > Therefore, add the option

Re: [PATCH mm] kfence: make reporting sensitive information configurable

2021-02-09 Thread Vlastimil Babka
On 2/9/21 4:13 PM, Marco Elver wrote: > 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. > > Therefore, add the option CONFIG_KFENCE_REPORT_SENSITIVE to decide if we > should add

[PATCH mm] kfence: make reporting sensitive information configurable

2021-02-09 Thread Marco Elver
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. Therefore, add the option CONFIG_KFENCE_REPORT_SENSITIVE to decide if we should add potentially sensitive information to KFENCE reports.