From: Thorsten Leemhuis <regressions@leemhuis.info>
To: regressions@lists.linux.dev
Cc: linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION 6.0.x / 6.1.x] NULL dereferencing at tracing #forregzbot
Date: Thu, 3 Nov 2022 13:54:04 +0100 [thread overview]
Message-ID: <2c6b195b-287c-c5de-8e22-72aed337af39@leemhuis.info> (raw)
In-Reply-To: <87h6zklb6n.wl-tiwai@suse.de>
[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]
On 31.10.22 08:11, Takashi Iwai wrote:
>
> 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?
Just adding this to the tracking:
#regzbot introduced f3ddb74ad07 ^
https://bugzilla.opensuse.org/show_bug.cgi?id=1204705
#regzbot title NULL dereferencing at tracing
#regzbot ignore-activity
#regzbot monitor:
https://lore.kernel.org/all/20221101191009.1e7378c8@rorschach.local.home/
Ciao, Thorsten
prev parent reply other threads:[~2022-11-03 12:54 UTC|newest]
Thread overview: 7+ 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
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 ` Thorsten Leemhuis [this message]
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=2c6b195b-287c-c5de-8e22-72aed337af39@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).