linux-kernel - Re: [PATCH] platform/x86: thinkpad_acpi: Handle KCOV _

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: <174980967013.26331.3871583437927541253.b4-ty@linux.intel.com>
Date: Fri, 13 Jun 2025 13:14:30 +0300
From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To: Kees Cook <kees@...nel.org>
Cc: Henrique de Moraes Holschuh <hmh@....eng.br>, 
 Hans de Goede <hdegoede@...hat.com>, ibm-acpi-devel@...ts.sourceforge.net, 
 platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org, 
 linux-hardening@...r.kernel.org
Subject: Re: [PATCH] platform/x86: thinkpad_acpi: Handle KCOV __init vs
 inline mismatches

On Thu, 29 May 2025 11:18:37 -0700, Kees Cook wrote:

> 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.
> 
> [...]


Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.

The list of commits applied:
[1/1] platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches
      commit: 6418a8504187dc7f5b6f9d0649c03e362cb0664b

--
 i.