linux-kernel - Re: dmaengine: CPU stalls while loading bluetooth module

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <56bb312e-5dca-4005-a388-c039646a9fa4@leemhuis.info>
Date: Mon, 29 Apr 2024 06:58:00 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@...mhuis.info>
To: Vinod Koul <vkoul@...nel.org>,
 Linux regressions mailing list <regressions@...ts.linux.dev>
Cc: dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org,
 parthiban@...umiz.com, saravanan@...umiz.com,
 'karthikeyan' <karthikeyan@...umiz.com>,
 "bumyong.lee" <bumyong.lee@...sung.com>
Subject: Re: dmaengine: CPU stalls while loading bluetooth module

On 29.04.24 06:49, Vinod Koul wrote:
> On 25-04-24, 12:03, Thorsten Leemhuis wrote:
>> On 28.03.24 16:06, Linux regression tracking (Thorsten Leemhuis) wrote:
>>> On 28.03.24 07:51, Vinod Koul wrote:
>>>> On 26-03-24, 14:50, Linux regression tracking (Thorsten Leemhuis) wrote:
>>>>>
>>>>> Vinod Koul, what's your option here? We have two reports about
>>>>> regressions caused by 22a9d958581244 ("dmaengine: pl330: issue_pending
>>>>> waits until WFP state") [v6.8-rc1] now:
>>>>>
>>>>> https://lore.kernel.org/lkml/1553a526-6f28-4a68-88a8-f35bd22d9894@linumiz.com/
>>>>>
>>>>> https://lore.kernel.org/all/ZYhQ2-OnjDgoqjvt@wens.tw/
>>>>> [the first link points to the start of this thread]
>>>>>
>>>>> To me it sounds like this is a change that better should be reverted,
>>>>> but you are of course the better judge here.
>>>>
>>>> Sure I have reverted this,
>>>
>>> Thx!
>>
>> That revert afaics has not made it to Linus yet. Is that intentional, or
>> did it just fell through the cracks?
> 
> Nope, it was sent to Linus last week and is now in -rc6...

Yeah, I noticed yesterday, as I otherwise would have mentioned it to
Linus. But it wasn't merged yet when I wrote the quoted mail. ;-)

Thx again!

Ciao, Thorsten