From: Steven Rostedt <rostedt@goodmis.org>
To: Christian Aurich Zanettini Martins <christian.aurichzm@gmail.com>
Cc: Vincent Donnefort <vdonnefort@google.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@kernel.org>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+fbe07bcf949966f3c00f@syzkaller.appspotmail.com
Subject: Re: [PATCH] ring-buffer: Do not WARN when trace_rb_cpu_prepare() fails to allocate
Date: Tue, 10 Nov 2026 04:25:17 -0500 [thread overview]
Message-ID: <20261110042517.5bbbe14b@fedora> (raw)
In-Reply-To: <CAPDkpGre=z=RCS_ffBKTKV_GsQn4ejyknVwNPFmjkhGTORZy5g@mail.gmail.com>
On Mon, 9 Nov 2026 07:38:55 -0300
Christian Aurich Zanettini Martins <christian.aurichzm@gmail.com> 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@gmail.com/
prev parent reply other threads:[~2026-11-10 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 22:25 [PATCH] ring-buffer: Do not WARN when trace_rb_cpu_prepare() fails to allocate Christian Aurich Zanettini Martins
2026-11-09 9:29 ` Vincent Donnefort
2026-11-09 10:38 ` Christian Aurich Zanettini Martins
2026-11-10 9:25 ` Steven Rostedt [this message]
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=20261110042517.5bbbe14b@fedora \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=christian.aurichzm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=syzbot+fbe07bcf949966f3c00f@syzkaller.appspotmail.com \
--cc=tglx@kernel.org \
--cc=vdonnefort@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.