From: Steven Rostedt <rostedt@goodmis.org>
To: Roland Ruckerbauer <roland.rucky@gmail.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
regressions@lists.linux.dev,
Steven Noonan <steven.noonan@gmail.com>
Subject: Re: [BUG] NULL pointer dereference probably caused by kernel/trace/ring_buffer.c
Date: Tue, 1 Nov 2022 17:38:02 -0400 [thread overview]
Message-ID: <20221101173802.7a476a04@rorschach.local.home> (raw)
In-Reply-To: <CAM6WdxfYU1Dc6dkMQMSGjgiggrziLvfwVPJV5OC02_AQO8YkVw@mail.gmail.com>
On Tue, 1 Nov 2022 21:07:20 +0100
Roland Ruckerbauer <roland.rucky@gmail.com> wrote:
> Meaning the rbwork pointer is not null, but also not a valid pointer.
> Subtracting offset of the wait_index gives me address 0x178, which
> sure seems wrong.
Hmm, I wonder if the buffer got freed somehow. Not sure how that would
happen, as you can't free the buffer if something is opened on it.
>
> I think I will try a gdb session with this kernel (but I have not done
> this for a long time, might take me a while to get it working).
If this is fully reproducible, could you run strace -f on rasdaemon to
see what it is doing before it crashed?
That could be very useful. At least I may be able to create a
reproducer, as my rasdaemon is working fine.
-- Steve
next prev parent reply other threads:[~2022-11-01 21:38 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
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 [this message]
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=20221101173802.7a476a04@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=roland.rucky@gmail.com \
--cc=steven.noonan@gmail.com \
--cc=tiwai@suse.de \
/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®