Daily Engineering Intelligence

Technology Newspaper

← Back to Home

Engineering Intelligence β€” Friday

September 25, 2026

πŸ”₯ What Changed

Platform-independent SIMD in Go

go.dev/blog (Sep 24) β€” Go 1.27 experimental platform- and size-agnostic simd package (GOEXPERIMENT=simd), loosely Highway-inspired. Portable vector types (simd.Float32s, simd.Uint8s, …) load/store from slices; write-once near-asm where hardware matches; emulate where SIMD/archsimd is missing. Explains why arch-dependent archsimd alone is hard (fixed vs runtime widths; mask-register vs vector-bitmask; AVX/AVX2/AVX512 vs NEON vs wasm gaps). Notes Green Tea GC already uses SIMD for mark scanning. Distinct from the already-briefed Stapelberg TurboPFor production archsimd case study β€” this is the project-authored API/design primary.

Why you care: Highest board weight (Go 50) and the first fresh official Go WC after two quiet days. Actionable for backends weighing cgo removal, crypto/data kernels, and simd vs archsimd/assembly. Frame as portable SIMD API literacy β€” not a Stapelberg rehash.
Read on go.dev β†’

🚨 How Cloudflare addressed a cross-tenant data exposure vulnerability in Containers

Cloudflare Blog (Sep 24) β€” Responsible disclosure (Sep 4) showed a Workers Paid customer could recover residual disk blocks from prior tenants’ Containers/Sandboxes on the same Firecracker host. Root cause: Linux dm-thin with pool option skip_block_zeroing. On delete, 64 KiB blocks returned to a shared pool; a small aligned 4 KiB write into an unmapped region allocated a reused 64 KiB block but only overwrote 4 KiB, leaving ~60 KiB of prior-tenant bytes readable via raw-device read. Mitigations: remove skip_block_zeroing fleet-wide and retire running disks + clear cached OCI image-layer dm-thin snapshots. Cleanup completed Sep 19; no evidence of malicious exploitation.

Impact: Workers Paid tenants on shared Containers/Sandboxes hosts could recover residual filesystem metadata / DB pages / application data from co-tenant residual blocks (not targetable to a specific victim). Who affected: Cloudflare Containers / Sandboxes multi-tenant hosts. Action required: none (fleet-fixed).

Why you care: Transferable lesson for any Firecracker/dm-thin multi-tenant disk pool: skip_block_zeroing is a silent cross-tenant leak class, and fixing allocate-path zeroing is incomplete without invalidating cached snapshot layers.
Read on Cloudflare β†’