mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: postix@posteo.eu
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, regressions@lists.linux.dev, tiwai@suse.de
Subject: Re: Fwd: [REGRESSION 6.0.x / 6.1.x] NULL dereferencing at tracing
Date: Wed,  2 Nov 2022 15:57:56 +0000	[thread overview]
Message-ID: <25d7e982-f959-d86c-a6e7-5efd1db1e75c@posteo.de> (raw)
In-Reply-To: <71829e56-a13f-0462-37a7-a4d64c16f561@posteo.de>

Hello everyone,

I have added lot's of debug printk's to see what's happening and I found 
that the "cpu" counter, which is used to access the buffer's array 
elements (cpu_buffer = buffer->buffers[cpu]) in the ring_buffer_wake_waiters
function, exceeds the maximum number of total of total cores, namely in 
my case 24, which means, it should only run from 0..23. However, upon 
debugging, it runs up to 31, and thus causing a NULL pointer dereference 
(&cpu_buffer->irq_work).

After adding a return statement in case cpu > 24, the bug is no longer 
reproducible.

You can find the diff between v6.1-rc2 and the patched version with 
added debug log in [1].
The corresponding dmesg output can be found in [2].

I hope this gives you a good hint to find the root cause!

[1] https://paste.opensuse.org/e60601aa
[2] https://paste.opensuse.org/bf1398ce



  reply	other threads:[~2022-11-02 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e693eb6b-28d0-d091-3df3-60f2b591c0e7@posteo.de>
2022-10-31 20:47 ` postix
2022-11-02 15:57   ` postix [this message]
2022-11-02 16:03     ` Steven Rostedt
2022-11-02 16:36       ` postix
2022-11-02 16:39         ` Steven Rostedt

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=25d7e982-f959-d86c-a6e7-5efd1db1e75c@posteo.de \
    --to=postix@posteo.eu \
    --cc=20221031144850.5522b036@rorschach.local.home \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --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®