Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <2c6b195b-287c-c5de-8e22-72aed337af39@leemhuis.info>
Date:   Thu, 3 Nov 2022 13:54:04 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.0
Subject: Re: [REGRESSION 6.0.x / 6.1.x] NULL dereferencing at tracing
 #forregzbot
Content-Language: en-US, de-DE
Cc:     linux-kernel@vger.kernel.org
References: <87h6zklb6n.wl-tiwai@suse.de>
To:     regressions@lists.linux.dev
From:   Thorsten Leemhuis <regressions@leemhuis.info>
In-Reply-To: <87h6zklb6n.wl-tiwai@suse.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

[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