All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: postix@posteo.eu
Cc: 20221031144850.5522b036@rorschach.local.home,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
	tiwai@suse.de
Subject: Re: [REGRESSION 6.0.x / 6.1.x] NULL dereferencing at tracing
Date: Wed, 2 Nov 2022 12:03:38 -0400	[thread overview]
Message-ID: <20221102120338.254741f7@rorschach.local.home> (raw)
In-Reply-To: <25d7e982-f959-d86c-a6e7-5efd1db1e75c@posteo.de>

On Wed,  2 Nov 2022 15:57:56 +0000
postix@posteo.eu wrote:

> 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).
> 

Could you add this patch.

 https://lore.kernel.org/all/20221101191009.1e7378c8@rorschach.local.home/

Thanks,

-- Steve


  reply	other threads:[~2022-11-02 16:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e693eb6b-28d0-d091-3df3-60f2b591c0e7@posteo.de>
2022-10-31 20:47 ` Fwd: [REGRESSION 6.0.x / 6.1.x] NULL dereferencing at tracing postix
2022-11-02 15:57   ` postix
2022-11-02 16:03     ` Steven Rostedt [this message]
2022-11-02 16:36       ` postix
2022-11-02 16:39         ` Steven Rostedt
2022-10-31  7:11 Takashi Iwai
2022-10-31  8:29 ` Steven Noonan
2022-10-31  9:48 ` Steven Rostedt
2022-10-31  9:52   ` Takashi Iwai
2022-10-31 18:48 ` Steven Rostedt
2022-11-01  8:21   ` Takashi Iwai

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=20221102120338.254741f7@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=20221031144850.5522b036@rorschach.local.home \
    --cc=linux-kernel@vger.kernel.org \
    --cc=postix@posteo.eu \
    --cc=regressions@lists.linux.dev \
    --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 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.