From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Kees Cook <kees@kernel.org>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Hans de Goede <hdegoede@redhat.com>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches
Date: Fri, 13 Jun 2025 13:14:30 +0300 [thread overview]
Message-ID: <174980967013.26331.3871583437927541253.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250529181831.work.439-kees@kernel.org>
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.
prev parent reply other threads:[~2025-06-13 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 18:18 [PATCH] platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches Kees Cook
2025-06-13 10:14 ` Ilpo Järvinen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=174980967013.26331.3871583437927541253.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.