Allow crc-fast to use version 1.8.0

[RobertSkawinski]

Currently the crc-fast crate version is pinned to 1.6.0, which breaks the backward compatibility implemented in crc-fast 1.8.0.
May I ask either to pin to crc-fast 1.8.0, or remove the version pinning?
VMs that does not passthrough host cpu information like proxmox in a HA setup with different cpu nodes are missing x86 features (SSE4.1 && PCLMULQDQ).

Related Ticket: #3981
Mentioned in file: rust-runtime/aws-smithy-checksums/Cargo.toml

I know there is a workaround for this, for example to patch inside Cargo.toml:

# Patch crc-fast to latest version (1.8.0+) which has improved runtime CPU feature detection
# and proper fallback to software implementation on older CPUs without SSE4.1/PCLMULQDQ
[patch.crates-io]
crc-fast = { git = "https://github.com/awesomized/crc-fast-rust" }

[vcjana]

Versions 1.4.0 through 1.8.0 contain an unfixed CPU feature detection bug causing SIGILL crashes in VMs without SSE4.1 and PCLMULQDQ support exactly what you're experiencing in Proxmox.

We're working on this from our side PR #4428 - this adds multi-architecture CI testing (x86_64 + ARM) to catch these issues before they reach production. This would have caught the crc-fast 1.4 bug before release. We're currently running tests on this PR.

[RobertSkawinski]

@vcjana Thank you so much for this clarification and reference to the wip PR. This helped me to understand the root cause of the wired behavior and the reason for locking the current state.

I have no more questions and I think this issue can be closed.