On Thu, Oct 19, 2023 at 01:22:38PM -0400, Brian Foster wrote: > BTW, should this code be protected from no free space situations at a > higher level, or should we consider a max retry count or something? I > want to be cautious about things like prospective livelocks > (particularly if this path is less common) if this retry was effectively > dead code due to not updating alloc_cursor.
It should be limiting itself to a single retry already: on retry, we set alloc_cursor = alloc_start, so we won't retry again. Just make sure that still works :)
