linux-kernel - Re: [PATCH] pinctrl: amd: Disable and mask interrupts on resume

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: <949fc214-3216-c012-0ddd-b6e1745c35ae@leemhuis.info>
Date:   Wed, 12 Apr 2023 12:47:58 +0200
From:   "Linux regression tracking (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
To:     Linus Walleij <linus.walleij@...aro.org>,
        Kornel Dulęba <korneld@...omium.org>
Cc:     Linux regressions mailing list <regressions@...ts.linux.dev>,
        gregkh@...uxfoundation.org,
        Basavaraj Natikar <Basavaraj.Natikar@....com>,
        Shyam Sundar S K <Shyam-sundar.S-k@....com>,
        upstream@...ihalf.com, rad@...ihalf.com, mattedavis@...gle.com,
        stable@...r.kernel.org, Sasha Levin <sashal@...nel.org>,
        "Gong, Richard" <richard.gong@....com>,
        Mario Limonciello <mario.limonciello@....com>,
        linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pinctrl: amd: Disable and mask interrupts on resume

On 11.04.23 22:44, Linus Walleij wrote:
> On Tue, Apr 11, 2023 at 3:35 PM Kornel Dulęba <korneld@...omium.org> wrote:
>> On Tue, Apr 11, 2023 at 3:29 PM Linux regression tracking (Thorsten
>> Leemhuis) <regressions@...mhuis.info> wrote:
> 
>>> Linusw, what's your preferred course to realize this revert quickly?
>>>
>>>  * someone (Kornel?) sends a revert with a commit msg for review, which
>>> you then apply and pass on to the other Linus?
>>>
>>>  * someone (Kornel?) sends a revert with a commit msg for review that
>>> immediately asks the other Linus to pick this up directly?
>>>
>>>  * we ask the other Linus directly to revert this (who then has to come
>>> up with a commit msg on his own)?
>>
>> Would you like me to send a reverting change?
>> I can do this right away.
> 
> Yeah that is best.
> 
>> The commit message would contain something like:
>>
>> This patch introduces a regression on Lenovo Z13, which can't wake
>> from the lid with it applied.
> 
> Looks good!
> 
> Thorsten: thanks for watching over this issue, we'll have it
> resolved pronto.

Thx for saying that, in cases like this there is always something in my
head that says "maybe the developers and maintainers would have done
everything just the same way and just as quickly, even if I hadn't made
so much annoying noise". But well, better save that sorry.

Side note: I sometimes wonder if reverts like this maybe should be send
directly to LinusT for mainlining with a ACK from the maintainer (e.g.
you in this case) to speed things up. Sure, having things in next for at
least a day (and running it through subsystem specific CI) can help
finding unexpected problems, but it delays things, too -- which
sometimes might result in a revert coming to late for a new stable
release. And that easily can mean that our users have to face known
issues for about one more week. :-/

Ciao, Thorsten

/me meanwhile wonders if Greg will still pick the revert up for the next
stable releases (currently in rc), if the revert reaches mainline before
they are released on Friday

/me will wait for the revert to hit mainline before he'll prod Greg
about it