linux-kernel - Re: Fwd: commit 9df9d2f0471b causes boot failure in pre-rc1 6.5 kernel

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <ef88e1e0-1276-971d-6302-13890cec9cac@leemhuis.info>
Date:   Sat, 1 Jul 2023 16:10:57 +0200
From:   "Linux regression tracking (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
To:     Bagas Sanjaya <bagasdotme@...il.com>,
        Linux regressions mailing list <regressions@...ts.linux.dev>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Fwd: commit 9df9d2f0471b causes boot failure in pre-rc1 6.5
 kernel

[dropping people from CC that likely don't care]

On 01.07.23 15:42, Bagas Sanjaya wrote:
> On 7/1/23 19:43, Linux regression tracking #update (Thorsten Leemhuis) wrote:
>> On 01.07.23 14:27, Bagas Sanjaya wrote:
>>> On Wed, Jun 28, 2023 at 09:06:22PM +0700, Bagas Sanjaya wrote:
>>>> I notice a regression report on Bugzilla [1]. Quoting from it:
>>> [....]
>>>> See Bugzilla for the full thread.
>>>>
>>>> #regzbot introduced: 9df9d2f0471b https://bugzilla.kernel.org/show_bug.cgi?id=217602
>>>> #regzbot title: early arch_cpu_finalize_init() cause immediate boot failure
>>> #regzbot fix: 0303c9729afc40
>>
>> Bagas, FWIW, there was no need for this at all. Regzbot would have
>> noticed that patch automatically due to the "Link:
>> https://bugzilla.kernel.org/show_bug.cgi?id=217602" in the patch
>> description (thx for this, tglx) once it landed in next or mainline
>> (just like it noticed
>> https://lore.kernel.org/lkml/168813193932.404.2885732890333911092.tip-bot2@tip-bot2/
>> earlier).
> 
> OK, thanks for another tip! I was doing above because at the time
> regzbot doesn't mark the regression as solved, so I had to manually
> told it.

regzbot could notice this sooner by monitoring all the for-linus and
for-next subsystem development trees. But I'm not sure if that's worth
it, because normally things that land there show up in -next within 24
hours anyway.

Ciao, Thorsten