[BUG] Error handling on memory allocation failure

[plbossart]

[BUG] Error handling on memory allocation failure

[kv2019i]

Btw this case of alloc failing is tracked in separate bug #8966

Let's use this to track how the error is reported to host.

[lgirdwood]

Added for v2.10, could be one of the cleanups.

[lyakh]

this is one of the effects of two co-existing error code families in the firmware: POSIX and IPC4

[kv2019i]

@lgirdwood @plbossart I don't understand why this is a production blocker. I agree it's a confusing error message, but an error is still reported.

[plbossart]

presumably in a production firmware, the memory allocation failure doesn't happen?
I think this is more for developers and integration phases, it's just very painful to make progress.

[kv2019i]

@plbossart Ack. I was perfectly fine with the v2.10 tag as this was/is slowing down development&debug. But now that the v2.10 window has closed, it's a different question whether this is something that will block the quarterly release, and my view is that it is not.
UPDATE: and to confirm, the actual alloc failure that prompted this bug, has been fixed #8966 -- so indeed in production releases, the alloc should never fail and any known such case should of course be fixed before any release.

[kv2019i]

No comment/responses, but as we are beyond rc1 and there's no case presented why this should block 2.10, moving to v2.11.