diff options
| author |   Kees Cook <kees@kernel.org> | 2025-07-17 16:25:12 -0700 |
|---|---|---|
| committer | Kees Cook <kees@kernel.org> | 2025-07-21 21:44:01 -0700 |
| commit | c64d6be1a6f8c93274bb861ec75c59453508093a (patch) | |
| tree | 125b12eff6d396d5b33ffbaa2336c7b3567f9ac4 /rust/pin-init/internal/src | |
| parent | arm: Handle KCOV __init vs inline mismatches (diff) | |
| download | wireguard-linux-c64d6be1a6f8c93274bb861ec75c59453508093a.tar.xz wireguard-linux-c64d6be1a6f8c93274bb861ec75c59453508093a.zip | |
s390: 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, we have to
handle differences in how GCC's inline optimizations get resolved. For
s390 this exposed a place where the __init annotation was missing but
ended up being "accidentally correct". Fix this cases and force a couple
functions to be inline with __always_inline.
Acked-by: Heiko Carstens <hca@linux.ibm.com>
Link: https://lore.kernel.org/r/20250717232519.2984886-7-kees@kernel.org
Signed-off-by: Kees Cook <kees@kernel.org>
Diffstat (limited to 'rust/pin-init/internal/src')
0 files changed, 0 insertions, 0 deletions