Thread Safety In Ringbuf Library

[WestCoastDaz]

I'm reviewing the ringbuf library for use with FreeRTOS across two threads and I can't see how the atomic operations implemented in the library make it thread safe.  The atomic operations seem to prevent multiple writers or multiple readers from accessing a ringbuf instance until a put or get operation is complete but how is this safe if a high priority task is the reading the buffer while a low priority task writes to the buffer?

Thanks,

Darren

[Krzysztof Chruscinski]

Hi Darren,

note that to read the buffer you only read wr_idx and modify (tmp_)rd_idx and wr_idx is updated when data is already in the buffer (in nrf_ringbuf_cpy_put or nrf_ringbuf_put). Can you describe exact case when high priority task could read invalid data?

regards,

Krzysztof