This is pre-existing and not changed by this patch: it only makes
explicit (via a checked `zerocopy` derive) what the previous `unsafe
impl transmute::{FromBytes, AsBytes}` already allowed implicitly -- the
layout is byte-identical and the message-handling path is untouched -- so
it neither introduces nor addresses this. I'm not familiar enough with
the GSP threat model to judge whether the TOCTOU is in scope here; if it
is worth noting, I can add a TODO comment near the affected reads.
- [PATCH RFC 0/4] rust: dma: bridge zerocopy-deriv... SeungJong Ha via B4 Relay
- [PATCH RFC 1/4] rust: transmute: add `impl_... SeungJong Ha via B4 Relay
- [PATCH RFC 2/4] rust: prelude: re-export `z... SeungJong Ha via B4 Relay
- [PATCH RFC 4/4] gpu: nova-core: gsp: conver... SeungJong Ha via B4 Relay
- Re: [PATCH RFC 4/4] gpu: nova-core: gsp... sashiko-bot
- Re: [PATCH RFC 4/4] gpu: nova-core:... SeungJong Ha
- Re: [PATCH RFC 4/4] gpu: nova-c... Alexandre Courbot
- Re: [PATCH RFC 4/4] gpu: n... SeungJong Ha
- Re: [PATCH RFC 4/4] gp... Alexandre Courbot
- [PATCH RFC 3/4] gpu: nova-core: gsp: derive... SeungJong Ha via B4 Relay
- Re: [PATCH RFC 0/4] rust: dma: bridge zeroc... Alexandre Courbot
- Re: [PATCH RFC 0/4] rust: dma: bridge z... Alistair Popple
- Re: [PATCH RFC 0/4] rust: dma: brid... Danilo Krummrich
- Re: [PATCH RFC 0/4] rust: dma: ... SeungJong Ha
- Re: [PATCH RFC 0/4] rust: dma: bridge z... SeungJong Ha
