[BUG] mbedtls "alt" functions return errors in a wrong way

[yamt]

Description / Steps to reproduce the issue

our mbedtls alt functions (eg.

nuttx-apps/crypto/mbedtls/source/sha1_alt.c

Lines 54 to 63 in 72668d7

	int mbedtls_sha1_update(FAR mbedtls_sha1_context *ctx,
	FAR const unsigned char *input,
	size_t ilen)
	{
	ctx->crypt.op = COP_ENCRYPT;
	ctx->crypt.flags |= COP_FLAG_UPDATE;
	ctx->crypt.src = (caddr_t)input;
	ctx->crypt.len = ilen;
	return cryptodev_crypt(ctx);
	}

)
return negative nuttx errno, while they should return mbedtls error code like MBEDTLS_ERR_SHA1_BAD_INPUT_DATA.

On which OS does this issue occur?

[OS: Mac]

What is the version of your OS?

macOS 15.5

NuttX Version

master

Issue Architecture

[Arch: xtensa]

Issue Area

[Area: Crypto]

Host information

No response

Verification

• I have verified before submitting the report.

[ThePassionate]

let me check sha1 test cases and aligning return values

[ThePassionate]

@yamt #3144 fix this issue and aligned error value with mbedtls test suits
firstly, with introduce of shax_update in header file like
https://github.com/Mbed-TLS/mbedtls/blob/v3.6.4/include/mbedtls/sha1.h#L130
There is no strict rule for the return value of this function. This is because the buildin implementation will not be wrong, so error value will not be obtained. However, in the official test set, there is indeed an illegal parameter check for the judgment parameters of the 'shax_starts' function. so i add the input value check and show result of test-suits in following
nsh> test_suite_shax
SHA-1 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/1 .................................... PASS
SHA-1 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/2 .................................... PASS
SHA-1 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/3 .................................... PASS
SHA-1 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/4 .................................... PASS
SHA-1 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/5 .................................... PASS
SHA-1 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/6 .................................... PASS
SHA-1 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/7 .................................... PASS
SHA-1 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/8 .................................... PASS
SHA-1 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/9 .................................... PASS
SHA-1 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/10 ................................... PASS
SHA-256 Invalid parameters ........................................ PASS
SHA-224 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/1 .................................. PASS
SHA-224 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/2 .................................. PASS
SHA-224 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/3 .................................. PASS
SHA-224 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/4 .................................. PASS
SHA-224 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/5 .................................. PASS
SHA-224 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/6 .................................. PASS
SHA-224 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/7 .................................. PASS
SHA-256 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/1 .................................. PASS
SHA-256 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/2 .................................. PASS
SHA-256 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/3 .................................. PASS
SHA-256 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/4 .................................. PASS
SHA-256 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/5 .................................. PASS
SHA-256 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/6 .................................. PASS
SHA-256 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/7 .................................. PASS
SHA-512 Invalid parameters ........................................ PASS
SHA-384 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/1 .................................. PASS
SHA-384 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/2 .................................. PASS
SHA-384 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/3 .................................. PASS
SHA-384 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/4 .................................. PASS
SHA-384 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/5 .................................. PASS
SHA-384 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/6 .................................. PASS
SHA-384 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/7 .................................. PASS
SHA-384 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/8 .................................. PASS
SHA-512 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/1 .................................. PASS
SHA-512 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/2 .................................. PASS
SHA-512 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/3 .................................. PASS
SHA-512 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/4 .................................. PASS
SHA-512 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/5 .................................. PASS
SHA-512 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/6 .................................. PASS
SHA-512 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/7 .................................. PASS
SHA-512 Test Vector NIST CAVS https://github.com/apache/nuttx-apps/pull/8 .................................. PASS

[yamt]

@yamt #3144 fix this issue and aligned error value with mbedtls test suits

thank you.

firstly, with introduce of shax_update in header file like
https://github.com/Mbed-TLS/mbedtls/blob/v3.6.4/include/mbedtls/sha1.h#L130
There is no strict rule for the return value of this function.

while there might not be strict rules, i guess we should avoid confusing users.
negative nuttx errno values badly conflict with MBEDTLS_ERR_xxx values and
confuses mbedtls_strerror.
for example, -EXDEV == -18 == MBEDTLS_ERR_GCM_AUTH_FAILED.

[ThePassionate]

@yamt #3144 fix this issue and aligned error value with mbedtls test suits

thank you.

firstly, with introduce of shax_update in header file like
https://github.com/Mbed-TLS/mbedtls/blob/v3.6.4/include/mbedtls/sha1.h#L130
There is no strict rule for the return value of this function.

while there might not be strict rules, i guess we should avoid confusing users. negative nuttx errno values badly conflict with MBEDTLS_ERR_xxx values and confuses mbedtls_strerror. for example, -EXDEV == -18 == MBEDTLS_ERR_GCM_AUTH_FAILED.

I get it. Let me map these to mbedtls error