linux-kernel - Re: [PATCH] ring-buffer: Do not trigger WARN_ON() due to a commit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250528114842.7b9e696a@gandalf.local.home>
Date: Wed, 28 May 2025 11:48:42 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Linux Trace Kernel
 <linux-trace-kernel@...r.kernel.org>, Mathieu Desnoyers
 <mathieu.desnoyers@...icios.com>, Vincent Donnefort <vdonnefort@...gle.com>
Subject: Re: [PATCH] ring-buffer: Do not trigger WARN_ON() due to a
 commit_overrun

On Wed, 28 May 2025 11:34:39 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> And even in that case, it triggers at most a couple of times a second:

Forgot to cut and paste:

[  367.010564] Ring buffer [1] commit overrun lost 1070 events at timestamp:367737571566
[  371.328151] Ring buffer [3] commit overrun lost 21442 events at timestamp:372051356588

This run had only two prints. I've had at most up to 8 prints for a test
that runs over a minute.

I updated the code to print the per CPU buffer it happened on as well as
the timestamp.

-- Steve