public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: regressions@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION 6.0.x / 6.1.x] NULL dereferencing at tracing
Date: Mon, 31 Oct 2022 05:48:37 -0400	[thread overview]
Message-ID: <20221031054837.3a101e75@rorschach.local.home> (raw)
In-Reply-To: <87h6zklb6n.wl-tiwai@suse.de>

On Mon, 31 Oct 2022 08:11:28 +0100
Takashi Iwai <tiwai@suse.de> wrote:

> Hi Steven,
> 
> we've got a bug report indicating the NULL dereference at the recent
> tracing changes, showing at the start of KDE.  The details including
> the dmesg are found at:
>   https://bugzilla.opensuse.org/show_bug.cgi?id=1204705
> 
> It was reported at first for 6.0.3, and confirmed that the problem
> persists with 6.1-rc, too.
> 
> The culprit seems to be the commit
> f3ddb74ad0790030c9592229fb14d8c451f4e9a8
>     tracing: Wake up ring buffer waiters on closing of the file
> and reverting it seems fixing the problem.
> 
> Could you take a look?
> 

Thanks for the report, can you send me your .config.

Thanks!

-- Steve

  parent reply	other threads:[~2022-10-31  9:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  7:11 [REGRESSION 6.0.x / 6.1.x] NULL dereferencing at tracing Takashi Iwai
2022-10-31  8:29 ` Steven Noonan
2022-10-31  9:48 ` Steven Rostedt [this message]
2022-10-31  9:52   ` Takashi Iwai
2022-10-31 18:48 ` Steven Rostedt
2022-11-01  8:21   ` Takashi Iwai
2022-11-03 12:54 ` [REGRESSION 6.0.x / 6.1.x] NULL dereferencing at tracing #forregzbot Thorsten Leemhuis
     [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
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=20221031054837.3a101e75@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox