diff options
| author | Ard Biesheuvel <ardb@kernel.org> | 2026-10-29 14:50:21 +0100 |
|---|---|---|
| committer | Catalin Marinas <catalin.marinas@arm.com> | 2026-11-19 00:10:14 +0000 |
| commit | ff049836f05f5e46f702858a7cb949998e85a310 (patch) | |
| tree | e27fd5ff65d9dacf83485a892c973313b75cc675 /rust/kernel/alloc/allocator | |
| parent | b059e957d07b3cab92eef4656988244043f5769a (diff) | |
lib/crc: Don't include <linux/types.h> in NEON intrinsics code
The kernel's definitions of uint64_t and int64_t in <linux/types.h> are based
on [unsigned] long long, whereas the ones provided by <stdint.h>, which is
included by <arm_neon.h>, are based on [unsigned] long on arm64. On 32-bit ARM,
a similar mismatch exists for intptr_t.
Including both into the same compilation unit currently only works because
asm/neon-intrinsics.h overrides the predefined macros that the compiler's
freestanding <stdint.h> uses to define these types. In order to be able to get
rid of those overrides, stop including <linux/types.h> into the CRC64 NEON
intrinsics code.
Instead, use <stddef.h> for the definition of size_t, and rely on
<asm/neon-intrinsics.h> to provide the u8 and u64 types used in the prototype
of crc64_nvme_neon(), which is shared with code that does include
<linux/types.h>. Use uint64_t for the arrays of constants that are passed to
vld1q_u64(), so that they match its prototype regardless of how uint64_t is
defined.
No change in generated code.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Tested-by: Nathan Chancellor <nathan@kernel.org>
Reviewed-by: Eric Biggers <ebiggers@kernel.org>
Cc: <stable@vger.kernel.org>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'rust/kernel/alloc/allocator')
0 files changed, 0 insertions, 0 deletions
