From: Steven Rostedt <rostedt@goodmis.org>
To: Roland Ruckerbauer <roland.rucky@gmail.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] NULL pointer dereference probably caused by kernel/trace/ring_buffer.c
Date: Mon, 31 Oct 2022 14:50:46 -0400 [thread overview]
Message-ID: <20221031145046.2a7f9d32@rorschach.local.home> (raw)
In-Reply-To: <CAM6Wdxc0KRJMXVAA0Y=u6Jh2V=uWB-_Fn6M4xRuNppfXzL1mUg@mail.gmail.com>
On Mon, 31 Oct 2022 14:02:12 +0100
Roland Ruckerbauer <roland.rucky@gmail.com> wrote:
> For me the crash is easily reproducible. For testing I run 6.0.5
> upstream kernel, but I guess everything since 6.0.3 is affected as
> well.
I'm looking into a path that calls this function without allocating the
buffer (when the file descriptor is released) I'm still looking to find
that path, but in the mean time, could you test this?
-- Steve
diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
index 199759c73519..c1c7ce4c6ddb 100644
--- a/kernel/trace/ring_buffer.c
+++ b/kernel/trace/ring_buffer.c
@@ -937,6 +937,9 @@ void ring_buffer_wake_waiters(struct trace_buffer *buffer, int cpu)
struct ring_buffer_per_cpu *cpu_buffer;
struct rb_irq_work *rbwork;
+ if (!buffer)
+ return;
+
if (cpu == RING_BUFFER_ALL_CPUS) {
/* Wake up individual ones too. One level recursion */
next prev parent reply other threads:[~2022-10-31 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 13:02 Roland Ruckerbauer
2022-10-31 13:24 ` Steven Rostedt
2022-10-31 18:50 ` Steven Rostedt [this message]
2022-10-31 20:20 ` Roland Ruckerbauer
2022-11-01 19:31 ` Steven Rostedt
2022-11-01 20:07 ` Roland Ruckerbauer
2022-11-01 21:38 ` Steven Rostedt
2022-11-01 21:50 ` Roland Ruckerbauer
2022-11-01 22:01 ` Roland Ruckerbauer
2022-11-01 22:35 ` Steven Rostedt
2022-11-01 22:43 ` Steven Rostedt
2022-11-01 23:00 ` Roland Ruckerbauer
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=20221031145046.2a7f9d32@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=roland.rucky@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®