Sashiko discussions
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	 "Liam R. Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	 Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>,
	 David Hildenbrand <david@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	 sashiko@lists.linux.dev,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH v3 00/40] mm: make VMA flag semantics explicit, eliminate VM_SPECIAL
Date: Fri, 25 Sep 2026 16:58:32 +0100	[thread overview]
Message-ID: <araV69I3WLn9I_Nu@gremlin> (raw)
In-Reply-To: <20260917-b4-mmap-prepare-vma-flag-sanify-v3-0-4583d8a23bca@kernel.org>

< 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

           reply	other threads:[~2026-09-25 15:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260917-b4-mmap-prepare-vma-flag-sanify-v3-0-4583d8a23bca@kernel.org>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=araV69I3WLn9I_Nu@gremlin \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=jannh@google.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pfalcato@suse.de \
    --cc=sashiko@lists.linux.dev \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox