On 04/04/2024 11:28, Philippe Mathieu-Daudé wrote:
Hi Mark,
On 24/3/24 20:16, Mark Cave-Ayland wrote:
Mark Cave-Ayland (17):
esp.c: move esp_fifo_pop_buf() internals to new esp_fifo8_pop_buf()
function
esp.c: replace esp_fifo_pop_buf() with esp_fifo8_pop_buf() in
Hi Mark,
On 24/3/24 20:16, Mark Cave-Ayland wrote:
Mark Cave-Ayland (17):
esp.c: move esp_fifo_pop_buf() internals to new esp_fifo8_pop_buf()
function
esp.c: replace esp_fifo_pop_buf() with esp_fifo8_pop_buf() in
do_command_phase()
esp.c: replace esp_fifo_pop_buf() with
On Sun, Mar 24, 2024 at 8:17 PM Mark Cave-Ayland
wrote:
> Patches 1-4 update existing users of esp_fifo_pop_buf() and esp_fifo_pop()
> with
> the internal cmdfifo to use the underlying Fifo8 device directly. The aim is
> to ensure that all the esp_fifo_*() functions only operate on the ESP's
>
[MCA: Since v1 I've received a few reports of FIFO assert()s being triggered
and a
cmdfifo buffer overflow discovered by fuzzing the updated ESP code. The
updating of
all FIFO push/pop operations to use the esp_fifo_*() functions in this series
provides protection against this, and in
