linux-kernel - Re: [PATCH] clocksource/drivers/exynos_mct: Fix section mismatch from the module conversion

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e8f1d209-fb35-4a39-941f-c81807ae91ff@kernel.org>
Date: Fri, 25 Jul 2025 10:52:20 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>, tglx@...utronix.de,
 willmcvicker@...gle.com
Cc: linux-kernel@...r.kernel.org, Alim Akhtar <alim.akhtar@...sung.com>,
 "moderated list:ARM/SAMSUNG S3C, S5P AND EXYNOS ARM ARCHITECTURES"
 <linux-arm-kernel@...ts.infradead.org>,
 "open list:ARM/SAMSUNG S3C, S5P AND EXYNOS ARM ARCHITECTURES"
 <linux-samsung-soc@...r.kernel.org>
Subject: Re: [PATCH] clocksource/drivers/exynos_mct: Fix section mismatch from
 the module conversion

On 25/07/2025 10:48, Krzysztof Kozlowski wrote:
> On 15/07/2025 14:18, Daniel Lezcano wrote:
>> The function register_current_timer_delay() when compiling on ARM32
>> fails with a section mismatch. That is resulting from the module
>> conversion where the function exynos4_clocksource_init() is called
>> from mct_init_dt(). This one had its __init annotation removed to for
>> the module loading.
>>
>> Fix this by adding the __init_or_module annotation for the functions:
>>  - mct_init_dt()
>>  - mct_init_spi()
>>  - mct_init_dt()
>>
>> Compiled on ARM32 + MODULES=no, ARM64 + MODULES=yes, ARM64 +
>> MODULES=no
>>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@...aro.org>
>> ---
>>  drivers/clocksource/exynos_mct.c | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> Did anyone applied this or any other fix?
> 
> Next builds are still broken.
> https://krzk.eu/#/builders/12/builds/3365

... and first failure was 9 (!) days ago:
https://krzk.eu/#/builders/12/builds/3350


Best regards,
Krzysztof