platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches
authorKees Cook <kees@kernel.org>
Thu, 29 May 2025 18:18:37 +0000 (11:18 -0700)
committerIlpo Järvinen <ilpo.jarvinen@linux.intel.com>
Fri, 13 Jun 2025 09:33:01 +0000 (12:33 +0300)
commit6418a8504187dc7f5b6f9d0649c03e362cb0664b
treee7f3c6ca6ef9f52f00c857769ce108148a23e739
parentda8f2708f9b69707f4efeb432a18395e46b4666f
platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches

When KCOV is enabled all functions get instrumented, unless the
__no_sanitize_coverage attribute is used. To prepare for
__no_sanitize_coverage being applied to __init functions[1], we have
to handle differences in how GCC's inline optimizations get resolved.
For thinkpad_acpi routines, this means forcing two functions to be
inline with __always_inline.

Link: https://lore.kernel.org/lkml/20250523043935.2009972-11-kees@kernel.org/
Signed-off-by: Kees Cook <kees@kernel.org>
Link: https://lore.kernel.org/r/20250529181831.work.439-kees@kernel.org
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
drivers/platform/x86/lenovo/thinkpad_acpi.c