On Thu, Feb 08, 2024 at 12:12:19PM +0100, Marco Elver wrote:
> git log --grep 'BUG: KFENCE: '
>
> There are more I'm aware of - also plenty I know of in downstream
> kernels (https://arxiv.org/pdf/2311.09394.pdf - Section 5.7).
Good.
> This is a problem shared by all other diagnostic and error reports the
> kernel produces.
Yes, and it becomes a problem if you expose it to the wider audience.
And yes, nothing new here - it is the same ol' question of getting good
bug reports.
> It's not a KASAN replacement, since it's sampling based.
I meant this: "Compared to KASAN, KFENCE trades performance for
precision."
And yeah, I did read what you pasted.
> From the Documentation: "KFENCE is designed to be enabled in
> production kernels, and has near zero performance overhead. Compared
> to KASAN, KFENCE trades performance for precision. The main motivation
> behind KFENCE's design, is that with enough total uptime KFENCE will
> detect bugs in code paths not typically exercised by non-production
> test workloads.
What is that double negation supposed to mean?
That it'll detect bugs in code paths that are typically exercised by
production test workloads?
> One way to quickly achieve a large enough total uptime is
> when the tool is deployed across a large fleet of machines."
In any case, I'll enable it on my test machines and see what happens.
> No reports are good. Doesn't mean absence of bugs though. :-)
As long as I don't know about them, I'm good. :-P
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
