linux-kernel - Re: Regression fix not progressing towards mainline/stable

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 for Android: free password hash cracker in your pocket

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

Date:   Tue, 8 Aug 2023 14:03:09 +0300
From:   Péter Ujfalusi <peter.ujfalusi@...ux.intel.com>
To:     Thorsten Leemhuis <regressions@...mhuis.info>,
        Takashi Iwai <tiwai@...e.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Bard Liao <yung-chuan.liao@...ux.intel.com>,
        Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
        Daniel Baluta <daniel.baluta@....com>
Cc:     sound-open-firmware@...a-project.org,
        LKML <linux-kernel@...r.kernel.org>,
        Linux kernel regressions list <regressions@...ts.linux.dev>,
        Alsa-devel <alsa-devel@...a-project.org>
Subject: Re: Regression fix not progressing towards mainline/stable

Hi Thorsten,

On 08/08/2023 09:10, Thorsten Leemhuis wrote:
> Hi everyone, I noticed a regression fix that afaics lingers in the
> thesofproject's git repo instead of progressing towards the stable trees
> and wondered what's up here.
>
> I'm talking about about the fix "ASoC: SOF: intel: hda: Clean up link
> DMA for IPC3 during stop" for this ticket:
> https://github.com/thesofproject/linux/issues/4455
> 
> Two more tickets about it:
> https://github.com/thesofproject/linux/issues/4482
> https://bugzilla.kernel.org/show_bug.cgi?id=217673
> 
> It seems the fix is ready and reviewed for two weeks now, but not even
> in -next by now. That's not how it should be for regression fixes, as
> per https://docs.kernel.org/process/handling-regressions.html it ideally
> should be in -stable soon or already. Is this a mistake, am I missing
> something, or is there a good reason for this?

We take regressions (and user reports) seriously and trying our best to
provide fixes asap.
We do prioritize bug fixes over features but in this case for some
reason the review process took longer than it usually does and the patch
has not been sent upstream. Patches must pass the review before they put
to the upstream queue.

I will be sending the fix in few minutes after testing it on top of next.

-- 
Péter