Re: [PATCH 6.12 000/172] 6.12.6-rc1 review

[Guenter Roeck <linux@roeck-us.net>]

On 12/18/24 06:56, Jiri Slaby wrote:
> On 18. 12. 24, 14:19, Naresh Kamboju wrote:
>> On Tue, 17 Dec 2024 at 22:55, Greg Kroah-Hartman
>> <gregkh@linuxfoundation.org> wrote:
>>>
>>> This is the start of the stable review cycle for the 6.12.6 release.
>>> There are 172 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 Thu, 19 Dec 2024 17:05:03 +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/v6.x/stable-review/patch-6.12.6-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-6.12.y
>>> and the diffstat can be found below.
>>>
>>> thanks,
>>>
>>> greg k-h
>>
>> The all i386 builds failed with the gcc-13 and clang-19
>> toolchain builds on following branches,
>>   - linux-6.12.y
>>   - linux-6.6.y
>>   - linux-6.1.y
>>   - linux-5.15.y
>>   - linux-5.10.y
>>
>> * i386, build
>>    - clang-19-defconfig
>>    - gcc-13-defconfig
>>
>> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>>
>> Build log:
>> -------------
>> i686-linux-gnu-ld: arch/x86/kernel/static_call.o: in function
>> `__static_call_update_early':
>> static_call.c:(.noinstr.text+0x15): undefined reference to
>> `static_call_initialized'
>>
>> The recent commit on this file is,
>>    x86/static-call: provide a way to do very early static-call updates
>>    commit 0ef8047b737d7480a5d4c46d956e97c190f13050 upstream.
> 
> Yes, the fix is at (via one hop):
> https://lore.kernel.org/all/aec47f97-c59b-403a-bf2a-d8551e2ec6f9@suse.com/
> 

The fix is not yet in mainline, meaning the offending patch now results
in the same build failure there.

Guenter