Is the the following scenario possible?
If I request a 4096 byte allocation, only one block (4096 bytes) is reserved at ptr and ptr+64 is returned (to account for the header?), so I only have 4096-64 bytes to use. If I understand correctly the reservation does not account for this and therefore a reservation right of the edge of a small/large request overflows. The same case applies when a new run is created.
I have applied the following workaround for now - increase requested size by 64 in nvm_reserve.
Is the the following scenario possible?
If I request a 4096 byte allocation, only one block (4096 bytes) is reserved at ptr and ptr+64 is returned (to account for the header?), so I only have 4096-64 bytes to use. If I understand correctly the reservation does not account for this and therefore a reservation right of the edge of a small/large request overflows. The same case applies when a new run is created.
I have applied the following workaround for now - increase requested size by 64 in nvm_reserve.