* Re: [PATCH v3 00/40] mm: make VMA flag semantics explicit, eliminate VM_SPECIAL
[not found] <20260917-b4-mmap-prepare-vma-flag-sanify-v3-0-4583d8a23bca@kernel.org>
@ 2026-09-25 15:58 ` Lorenzo Stoakes (ARM)
0 siblings, 0 replies; only message in thread
From: Lorenzo Stoakes (ARM) @ 2026-09-25 15:58 UTC (permalink / raw)
To: Andrew Morton, Liam R. Howlett, Vlastimil Babka, Jann Horn,
Pedro Falcato, David Hildenbrand, Suren Baghdasaryan
Cc: linux-mm, linux-kernel, sashiko, Konstantin Ryabitsev
< Edit mailing list, +sashiko as I gather this kind of feedback is wanted? :) >
I usually don't report it, but here's an example of some false positives, which
sashiko regenerates on respin.
Specifically the 2/40 (high) report was valid, as raised by Gregory and now
addressed ready for v4.
The ones on 1/40 (high), the other 2 on 4/40 (medium, medium) and the one on
24/40 (low) were all just wrong.
The one on 8/40 is bit but had some semblence of logic, but still not something
I'll take action on.
So a false positive rate of 83.3% here, or 67.7% if you exclude the 'meh' one.
In general I've continued to find the rate to be 50% at best, and it has not
improved over time.
It also seems that low/medium reports (which I think were disabled before?) are
particularly bad.
(I thought those were previously disabled for being inaccurate?)
I realise everybody is busy, but it'd be nice to have a means of marking
individual reports as hallucinations.
Thanks!
--
Cheers, Lorenzo
^ permalink raw reply [flat|nested] only message in thread