Hmm, that's really unfortunate. Applications really should be prepared
for
failing brk(), as there is no guarantee provided by anyobody whatsoever
about the space allocated for the program break.
Heck, even my manpage tells me:
"Avoid using brk() and sbrk(): the malloc(3) memory allocation package
is
the portable and comfortable way of allocating memory."
--
Jiri Kosina
SUSE Labs
Hello Jiri,
I slightly looked at patch, does it have any drawbacks?
If I understand correctly, this simply fix could avoid
bloat from musl-libc and should be better way than actual status.
Is there any reason to not include this patch?
Thank you
David
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
