linux-kernel - Re: [PATCH RFC/RFT 08/12] clk: samsung: exynos990: Use platform_driver_probe() to avoid _

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] [day] [month] [year] [list]

Message-Id: <D8BS7PJ6LNYY.28AK1FF2MR85S@mentallysanemainliners.org>
Date: Sun, 09 Mar 2025 14:49:32 +0100
From: "Igor Belwon" <igor.belwon@...tallysanemainliners.org>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@...aro.org>, "Krzysztof
 Kozlowski" <krzk@...nel.org>, "Sylwester Nawrocki"
 <s.nawrocki@...sung.com>, "Chanwoo Choi" <cw00.choi@...sung.com>, "Alim
 Akhtar" <alim.akhtar@...sung.com>, "Michael Turquette"
 <mturquette@...libre.com>, "Stephen Boyd" <sboyd@...nel.org>, "Sam
 Protsenko" <semen.protsenko@...aro.org>, "Peter Griffin"
 <peter.griffin@...aro.org>, André Draszik
 <andre.draszik@...aro.org>, "Tudor Ambarus" <tudor.ambarus@...aro.org>
Cc: <linux-samsung-soc@...r.kernel.org>, <linux-clk@...r.kernel.org>,
 <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC/RFT 08/12] clk: samsung: exynos990: Use
 platform_driver_probe() to avoid __refdata

On Wed Mar 5, 2025 at 10:43 PM CET, Krzysztof Kozlowski wrote:
> Switch registering platform driver to platform_driver_probe(), so the
> 'struct platform_driver' can be properly discarded after init and there
> won't be need of __refdata to silence DEBUG_SECTION_MISMATCH.
>
> The change requires using subsys_initcall instead of core_initcall,
> because no device drivers would bound in the latter, as required by
> platform_driver_probe().
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>

Hi Krzysztof and apologies for the delay in testing.

On my Exynos990 platforms this patch causes similar oopses to those
sent by André (different places each boot). I am unable to get the logs from
UART right now though (refactoring my testing setup). Apologies.

So this bug seems to be platformwide :(

Best regards,
Igor