linux-kernel - Re: Fwd: Kernel 6.6.1 hangs on "loading initial ramdisk"

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: <7cf21703-391a-4123-b862-14a1af62aeaa@gmail.com>
Date:   Sun, 10 Dec 2023 14:30:08 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Linux regressions mailing list <regressions@...ts.linux.dev>,
        Ard Biesheuvel <ardb@...nel.org>,
        Borislav Petkov <bp@...en8.de>,
        Thorsten Leemhuis <regressions@...mhuis.info>
Cc:     bwg <whirl@...otilta.ca>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-efi <linux-efi@...r.kernel.org>,
        the arch/x86 maintainers <x86@...nel.org>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Ingo Molnar <mingo@...hat.com>,
        Thomas Gleixner <tglx@...utronix.de>, shibedrill1@...il.com
Subject: Re: Fwd: Kernel 6.6.1 hangs on "loading initial ramdisk"

On 12/10/23 14:15, Linux regression tracking (Thorsten Leemhuis) wrote:
> [Moved a lot of people CCed in the previous mail to BCC, as I'm pretty
> sure they do not care about this regression; at the same time add the
> x86 maintainers and the efi list.]
> 
> [Top posting for once to make this easier accessible for everyone.]
> 
> Ard, Boris, just to make it obvious: the regression report quoted below
>  was bisected to a1b87d54f4e45f ("x86/efistub: Avoid legacy decompressor
> when doing EFI boot") [v6.6-rc1] from Ard which committed by Boris.
> There are two users that seem to be affected by this. Both seem to run
> Arch. For details see:
> https://bugzilla.kernel.org/show_bug.cgi?id=218173
> 
> Bagas, FWIW, I know you want to help, but your previous mail is not
> helpful at all -- on the contrary, as it is yet another one that is
> likely hurting my regression tracking efforts[1]. Please stop and just
> tell me about things like this in a private mail, as we agreed on earlier.
> 
> Ciao, Thorsten
> 
> [1] This is why: You just added Ard and Boris to the CC, but did not
> make it obvious *why* they should care about that mail. They (and all
> the other recipients) for sure will have no idea what a1b87d54f4e45f
> exactly is, so you should have mentioned the commit summary. And doing
> that after a big quote makes it worse, as many people now need to scroll
> down to see if that mails contains something that might be relevant for
> them -- and just a waste of time if not.
> 
> Furthermore, sending the first mail of the thread to all those people
> and lists was likely not very wise, as nobody is likely to care in a
> case like this. And not removing all those people and lists in the
> second mail of the thread make it a lot worse, as it became clear that
> many people and list do not care about it now that the regression was
> bisected. Hence it's best to remove them, we all get enough mail already.
> 
> All that makes people ignore mails from you -- and maybe about
> regression tracking in general. :-(
> 

Oops, I didn't greet additional Cc's as you mentioned (that's my
tendency when handling regressions).

So maybe we continue tracking this on Bugzilla or keeping on ML or
both?

Thanks.

-- 
An old man doll... just what I always wanted! - Clara