In the wrappers around calls to SIMD operations, explicitly mark the
output memory as being initialized for KMSAN. Found with KMSAN.
Sponsored by: Netflix
Assisted-By: Claude Code - Opus 5 (1M context)
Details
Details
Diff Detail
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Skipped - Unit
Tests Skipped - Build Status
Buildable 77238 Build 74121: arc lint + arc unit
Event Timeline
| sys/contrib/openzfs/include/os/linux/spl/sys/simd.h | ||
|---|---|---|
| 30 | This is a relatively new header in Linux, I'm not sure if it's ok to include it here. | |
| sys/contrib/openzfs/module/icp/algs/blake3/blake3_impl.c | ||
| 51 | cv is also used as an input, so how can it be uninitialized to begin with? Same question for the other compress_in_place ops. | |
| sys/contrib/openzfs/module/icp/algs/sha2/sha256_impl.c | ||
| 51 | Why exactly is this needed? Isn't the state already initialized by C code in SHA2Init()? | |