Re: [PATCH] ring-buffer: Do not WARN when trace_rb_cpu_prepare() fails to allocate
From: Steven Rostedt
Date: Tue Nov 10 2026 - 04:56:26 EST
On Mon, 9 Nov 2026 07:38:55 -0300
Christian Aurich Zanettini Martins <christian.aurichzm@xxxxxxxxx> wrote:
> Thanks Vincent. I took that reply as Steven explaining where the warning
> comes from, but I may have misread it.
>
> Steven, the same si_mem_available() check fails silently for the current
> CPU in alloc_buffer(), so whether mkdir WARNs or just returns -ENOMEM
> depends on which CPU runs out first. If you'd rather keep the WARN I'll
> drop this.
Actually, because of the CPU coming on line (not the instances) I
pulled it into my test queue. I'm currently traveling so I haven't
pushed things up yet. But patchwork has updated the status[1] of this to
"Under review" which means it's in the testing process.
-- Steve
[1] https://patchwork.kernel.org/m/20261104222558.863948-1-christian.aurichzm@xxxxxxxxx/