Jonas Jonsson

Possible memory leak in ota_pal.c (CA-296)

2

In the function [otaPal_CheckFileSignature()](https://github.com/espressif/esp-aws-iot/blob/1fc7681778bc271960a4e3db514a209df0380917/libraries/ota-for-aws-iot-embedded-sdk/port/ota_pal.c#L403) there are two possible code paths that lead to memory leaks. The call to [CRYPTO_SignatureVerificationStart](https://github.com/espressif/esp-aws-iot/blob/1fc7681778bc271960a4e3db514a209df0380917/libraries/ota-for-aws-iot-embedded-sdk/port/ota_pal.c#L413) will allocate memory but it's not freed until [CRYPTO_SignatureVerificationFinal()](https://github.com/espressif/esp-aws-iot/blob/1fc7681778bc271960a4e3db514a209df0380917/libraries/ota-for-aws-iot-embedded-sdk/port/ota_pal.c#L460) is called....

The expected fstab syntax doesn't work since commit 3da0b6cb55871b209218f1b64b5b8d60ac5f9ac5. Something like this used to work with the 1.3 release. `/mnt/src /mnt/target fuse.rofs-filtered allow_other,ro 0 0` For some reason the source...

This restores the old 1.3 behavior and allow the source directory to be specified as a positional argument. This make the regular fstab syntax work correctly. For example /mnt/src /mnt/target...

fix(freertos): Avoid core switch deadlock on start (IDFGH-15509)

2

## Description With CONFIG_ESP_MAIN_TASK_AFFINITY_NO_AFFINITY=y the main task could switch core between registering the idle hook and the while loop. This would cause a deadlock were the current task was waiting...