> QAT HW generates bytes of 0x00 digest, even when a digest of len 0 is
> requested for NULL. This caused test failures when the test vector had
> digest len 0, as the buffer has unexpected changed bytes.
>
> By placing the digest into the cookie for NULL authentication,
> the buffer remains unchanged as expected, and the digest
> is placed to the side, as it won't be used anyway.
>
> This fix was previously added for the main QAT code path, but it also
> needs to be included for the raw API code path.
>
> Fixes: db0e952a5c01 ("crypto/qat: add NULL capability")
> Cc: sta...@dpdk.org
>
> Signed-off-by: Ciara Power <ciara.po...@intel.com>
Applied to dpdk-next-crypto
Thanks.
