tree fe0bb72156c5c5eddfa12f835fbb94487112bfbd
parent f0daff971b7b48c39939a30be9e4491f08006081
author Gilles Peskine <Gilles.Peskine@arm.com> 1738780912 +0100
committer Gilles Peskine <Gilles.Peskine@arm.com> 1746636119 +0200

Initialize driver context in setup functions

In API functions that set up a multipart or interruptible operation, make
sure to initialize the driver-specific part of the context. This is a union,
and initializing the union to `{0}` only guarantees that the first member of
the union is initialized, not necessarily the member used by the driver.
Most compilers do initialize the whole union to all-bits-zero, but some
don't. With compilers that don't, the lack of initialization caused failures
of built-in MAC, interruptible-sign and interruptible-verify. It could also
cause failures for other operations with third-party drivers: we promise
that drivers' setup entry points receive a zero-initialized operation
structure, but this promise was not kept.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>