The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: elver@google.com, dvyukov@google.com
Cc: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
	 kernel-team@meta.com
Subject: RFC: KCSAN single report "feature"
Date: Tue, 7 Jul 2026 07:34:42 -0700	[thread overview]
Message-ID: <ak0Mw9-R23t9ltkt@gmail.com> (raw)

Hello Marco and KCSAN community

KCSAN rate-limits reports so that a given data race is printed at most once
per CONFIG_KCSAN_REPORT_ONCE_IN_MS (3s by default): duplicates within that
window are dropped, but once it elapses the race is printed again in full.

On a long-running machine a persistent race therefore reprints the same
multi-line report every few seconds for as long as the racy code runs, flooding
dmesg/netconsole with identical reports and drowning out genuinely new ones.

Raising REPORT_ONCE_IN_MS only widens the window — the full report still
eventually recurs — and setting it to 0 disables rate limiting entirely, so
there is no way today to get a race reported just once.

I have some debug kernel running in my of Meta fleet, with these debug features
and I would like to enable KCSAN, but, this behaviour is flooding our data
pipeline.

I've recently solved something similar on kmemleak and I am wondering if there
is interested in solving something similar on KCSAN.

	77d100d11c87e mm/kmemleak: dedupe verbose scan output by allocation backtrace

Would it be OK to have a "report once" mode that prints each race once and never
re-reports it,  maybe exposed as a bool CONFIG_KCSAN_REPORT_ONCE or a
kcsan.report_once module parameter ?

Thanks,
--breno

             reply	other threads:[~2026-07-07 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 14:34 Breno Leitao [this message]
2026-07-07 21:36 ` RFC: KCSAN single report "feature" Marco Elver

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=ak0Mw9-R23t9ltkt@gmail.com \
    --to=leitao@debian.org \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.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