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
Originally, there was logic like the following for KERNEL mode in mm/mm_heap/:
brkaddr = sbrk(size);
When we modified this to handle the case of size == 0, this became:
brkaddr = sbrk(size < 1 ? 1 : size);
But there still could be an issue here. Not just for size < 1 for for all sizes. The sizes don't include quantization overhead, or the overhead from the memory header. So the amount of memory requested is smaller than that which is actually needed. If nothing else, that does leave me a little uneasy.
But I have not looked at the detailed logic in sbrk to see how it handles the size. Perhaps there is no problem. This issue is simply to verify that that is the case.
As has been pointed out MM_MIN_CHUNK is not valid for tlsf_realloc(). But even if tlsf_realloc() and mm_realloc() are different in this way, that would not change the issue, that would just make any solution that might be needed more difficult (and I'm not even certain that any solution is needed).
The text was updated successfully, but these errors were encountered:
Originally, there was logic like the following for KERNEL mode in
mm/mm_heap/
:When we modified this to handle the case of size == 0, this became:
But there still could be an issue here. Not just for
size < 1
for for all sizes. The sizes don't include quantization overhead, or the overhead from the memory header. So the amount of memory requested is smaller than that which is actually needed. If nothing else, that does leave me a little uneasy.I am thinking it should be like:
But I have not looked at the detailed logic in
sbrk
to see how it handles the size. Perhaps there is no problem. This issue is simply to verify that that is the case.As has been pointed out
MM_MIN_CHUNK
is not valid fortlsf_realloc()
. But even iftlsf_realloc()
andmm_realloc()
are different in this way, that would not change the issue, that would just make any solution that might be needed more difficult (and I'm not even certain that any solution is needed).The text was updated successfully, but these errors were encountered: