linux-kernel - Re: Kernel 6.4-rc1 ARM boot fails

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]

Date:   Sun, 14 May 2023 15:14:58 +0200
From:   "Linux regression tracking #adding (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
To:     Colin Foster <colin.foster@...advantage.com>,
        Ard Biesheuvel <ardb@...nel.org>
Cc:     linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Linus Walleij <linus.walleij@...aro.org>,
        "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>,
        Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: Kernel 6.4-rc1 ARM boot fails

[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]

On 10.05.23 08:30, Colin Foster wrote:
> 
> I just wanted to give a heads up. I tested 6.4-rc1 on a Beaglebone Black
> and kept getting boot hangs. A bisect led me to commit c76c6c4ecbec ("ARM:
> 9294/2: vfp: Fix broken softirq handling with instrumentation enabled").
>
> The dying message is "Run /sbin/init as init process"
> 
> I'm not sure if this has already been reported. I was able to revert this
> patch and confirm things work again.
> [...]

Thanks for the report. I know a fix is incoming, but to be sure the
issue doesn't fall through the cracks unnoticed, I'm adding it to
regzbot, the Linux kernel regression tracking bot:

#regzbot ^introduced c76c6c4ecbec
#regzbot title arm32: tons of different boot time errors
#regzbot ignore-activity
#regzbot monitor:
https://lore.kernel.org/all/000000000000d3001a05faf979c8@google.com/
#regzbot fix ARM: 9297/1: vfp: avoid unbalanced stack on 'success'
return path
#regzbot monitor:
https://lore.kernel.org/all/20230506161325.223362-1-ardb@kernel.org/

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.