From: Florian Fainelli <f.fainelli@gmail.com>
To: "Daniel Díaz" <daniel.diaz@linaro.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, sudipm.mukherjee@gmail.com,
slade@sladewatkins.com
Subject: Re: [PATCH 4.9 00/24] 4.9.306-rc1 review
Date: Wed, 9 Mar 2022 19:32:03 -0800 [thread overview]
Message-ID: <917e2fb6-d91a-8ef6-62c0-920271ca2cd4@gmail.com> (raw)
In-Reply-To: <322280c2-8673-949c-ffd4-4e804a030b89@linaro.org>
On 3/9/2022 11:18 AM, Daniel Díaz wrote:
> Hello!
>
> On 09/03/22 12:40, Daniel Díaz wrote:
>> Hello!
>>
>> On 09/03/22 09:59, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 4.9.306 release.
>>> There are 24 patches in this series, all will be posted as a response
>>> to this one. If anyone has any issues with these being applied, please
>>> let me know.
>>>
>>> Responses should be made by Fri, 11 Mar 2022 15:58:48 +0000.
>>> Anything received after that time might be too late.
>>>
>>> The whole patch series can be found in one patch at:
>>> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.306-rc1.gz
>>>
>>> or in the git tree and branch at:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>>> linux-4.9.y
>>> and the diffstat can be found below.
>>>
>>> thanks,
>>>
>>> greg k-h
>>
>> Regressions found.
>>
>> The following Arm combinations fail to build:
>> - arm-gcc-8-bcm2835_defconfig
>> - arm-gcc-8-imx_v6_v7_defconfig
>> - arm-gcc-8-omap2plus_defconfig
>> - arm-gcc-9-bcm2835_defconfig
>> - arm-gcc-9-imx_v6_v7_defconfig
>> - arm-gcc-9-omap2plus_defconfig
>> - arm-gcc-10-bcm2835_defconfig
>> - arm-gcc-10-imx_v6_v7_defconfig
>> - arm-gcc-10-omap2plus_defconfig
>> - arm-gcc-11-bcm2835_defconfig
>> - arm-gcc-11-imx_v6_v7_defconfig
>> - arm-gcc-11-omap2plus_defconfig
>>
>> Messages look like this:
>>
>> /builds/linux/arch/arm/kernel/entry-common.S: Assembler messages:
>> /builds/linux/arch/arm/kernel/entry-common.S:155: Error:
>> co-processor register expected -- `mcr p15,0,r0,c7,r5,4'
>> /builds/linux/arch/arm/kernel/entry-common.S:164: Error:
>> co-processor register expected -- `mcr p15,0,r0,c7,r5,4'
>> make[2]: *** [/builds/linux/scripts/Makefile.build:407:
>> arch/arm/kernel/entry-common.o] Error 1
>> /builds/linux/arch/arm/kernel/entry-armv.S: Assembler messages:
>> /builds/linux/arch/arm/kernel/entry-armv.S:1124: Error:
>> co-processor register expected -- `mcr p15,0,r0,c7,r5,4'
>> /builds/linux/arch/arm/kernel/entry-armv.S:1147: Error:
>> co-processor register expected -- `mcr p15,0,r0,c7,r5,4'
>> /builds/linux/arch/arm/kernel/entry-armv.S:1170: Error:
>> co-processor register expected -- `mcr p15,0,r0,c7,r5,4'
>> /builds/linux/arch/arm/kernel/entry-armv.S:1193: Error:
>> co-processor register expected -- `mcr p15,0,r0,c7,r5,4'
>> /builds/linux/arch/arm/kernel/entry-armv.S:1232: Error:
>> co-processor register expected -- `mcr p15,0,r0,c7,r5,4'
>> make[2]: *** [/builds/linux/scripts/Makefile.build:407:
>> arch/arm/kernel/entry-armv.o] Error 1
>> /builds/linux/arch/arm/mm/cache-v7.S: Assembler messages:
>> /builds/linux/arch/arm/mm/cache-v7.S:63: Error: co-processor
>> register expected -- `mcr p15,0,r0,c7,r5,4'
>> /builds/linux/arch/arm/mm/cache-v7.S:136: Error: co-processor
>> register expected -- `mcr p15,0,r0,c7,r5,4'
>> /builds/linux/arch/arm/mm/cache-v7.S:170: Error: co-processor
>> register expected -- `mcr p15,0,r0,c7,r5,4'
>> /builds/linux/arch/arm/mm/cache-v7.S:298: Error: co-processor
>> register expected -- `mcr p15,0,r0,c7,r5,4'
>> make[2]: *** [/builds/linux/scripts/Makefile.build:407:
>> arch/arm/mm/cache-v7.o] Error 1
>> /builds/linux/arch/arm/mm/tlb-v7.S: Assembler messages:
>> /builds/linux/arch/arm/mm/tlb-v7.S:88: Error: co-processor register
>> expected -- `mcr p15,0,r0,c7,r5,4'
>> make[2]: *** [/builds/linux/scripts/Makefile.build:407:
>> arch/arm/mm/tlb-v7.o] Error 1
>> /builds/linux/arch/arm/mm/proc-v7-2level.S: Assembler messages:
>> /builds/linux/arch/arm/mm/proc-v7-2level.S:58: Error: co-processor
>> register expected -- `mcr p15,0,r0,c7,r5,4'
>> /builds/linux/arch/arm/mm/proc-v7-2level.S:60: Error: co-processor
>> register expected -- `mcr p15,0,r0,c7,r5,4'
>> /builds/linux/arch/arm/mm/proc-v7.S:61: Error: co-processor
>> register expected -- `mcr p15,0,r0,c7,r5,4'
>> make[2]: *** [/builds/linux/scripts/Makefile.build:407:
>> arch/arm/mm/proc-v7.o] Error 1
>> make[2]: Target '__build' not remade because of errors.
>
> Here's what the bisection throws for this one:
Here is the fix:
https://lore.kernel.org/linux-arm-kernel/E1nS1fu-00GcNN-24@rmk-PC.armlinux.org.uk/
--
Florian
next prev parent reply other threads:[~2022-03-10 3:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 15:59 [PATCH 4.9 00/24] 4.9.306-rc1 review Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 01/24] x86/speculation: Add RETPOLINE_AMD support to the inline asm CALL_NOSPEC variant Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 02/24] x86/retpoline: Make CONFIG_RETPOLINE depend on compiler support Greg Kroah-Hartman
2022-03-09 19:58 ` Ben Hutchings
2022-03-09 22:39 ` Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 03/24] x86/retpoline: Remove minimal retpoline support Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 04/24] Documentation: Add section about CPU vulnerabilities for Spectre Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 05/24] Documentation: Add swapgs description to the Spectre v1 documentation Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 06/24] Documentation: refer to config RANDOMIZE_BASE for kernel address-space randomization Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 07/24] x86/speculation: Merge one test in spectre_v2_user_select_mitigation() Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 08/24] x86,bugs: Unconditionally allow spectre_v2=retpoline,amd Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 09/24] x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 10/24] x86/speculation: Add eIBRS + Retpoline options Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 11/24] Documentation/hw-vuln: Update spectre doc Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 12/24] x86/speculation: Include unprivileged eBPF status in Spectre v2 mitigation reporting Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 13/24] x86/speculation: Use generic retpoline by default on AMD Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 14/24] x86/speculation: Update link to AMD speculation whitepaper Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 15/24] x86/speculation: Warn about Spectre v2 LFENCE mitigation Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 16/24] x86/speculation: Warn about eIBRS + LFENCE + Unprivileged eBPF + SMT Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 17/24] arm/arm64: Provide a wrapper for SMCCC 1.1 calls Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 18/24] arm/arm64: smccc/psci: add arm_smccc_1_1_get_conduit() Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 19/24] ARM: report Spectre v2 status through sysfs Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 20/24] ARM: early traps initialisation Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 21/24] ARM: use LOADADDR() to get load address of sections Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 22/24] ARM: Spectre-BHB workaround Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 23/24] ARM: include unprivileged BPF status in Spectre V2 reporting Greg Kroah-Hartman
2022-03-09 15:59 ` [PATCH 4.9 24/24] ARM: fix build error when BPF_SYSCALL is disabled Greg Kroah-Hartman
2022-03-09 18:40 ` [PATCH 4.9 00/24] 4.9.306-rc1 review Daniel Díaz
2022-03-09 19:18 ` Daniel Díaz
2022-03-10 3:32 ` Florian Fainelli [this message]
2022-03-10 11:41 ` Pavel Machek
2022-03-10 11:48 ` Greg Kroah-Hartman
2022-03-09 20:26 ` Shuah Khan
2022-03-10 3:45 ` Florian Fainelli
2022-03-10 11:39 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=917e2fb6-d91a-8ef6-62c0-920271ca2cd4@gmail.com \
--to=f.fainelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.diaz@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=slade@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).