You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If the system opens the ESP_AT_CIPDINFO_USE option, when the host side
reboot may receive some invalid IPD information (esp32 has not been restarted),
at this time, because the system has just booted up, IPD in the link id does
not exist in the host side, it will execute the following code, but due to the
return value checking logic is incorrect, and continue to use the null pointer
to cause the system to crash.
The code for checking the null pointer is incorrect,
with ESP_AT_CIPDINFO_USE turned on, after a soft reboot
of the host and before a reboot of ESP32, the host may
receive an incorrect IPD message causing a system crash.
Fixeszephyrproject-rtos#81804
Signed-off-by: Hongquan Li <[email protected]>
Describe the bug
If the system opens the ESP_AT_CIPDINFO_USE option, when the host side
reboot may receive some invalid IPD information (esp32 has not been restarted),
at this time, because the system has just booted up, IPD in the link id does
not exist in the host side, it will execute the following code, but due to the
return value checking logic is incorrect, and continue to use the null pointer
to cause the system to crash.
Expected behavior
The system is booting up normally.
Impact
Until the host side restarts esp32, the host side may receive some messages from IPD causing the system to crash
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: