4 ms·
I can imagine the future memcpy CVE: "arguments to memcpy to regions not previously allocated or after having been freed can potentially cause security issues.
by jhallenworld 3y ago
I can imagine the future memcpy CVE: "arguments to memcpy to regions not previously allocated or after having been freed can potentially cause security issues. Therefore we propose that memcpy check its arguments against this new list of valid memory addresses that we are now going to keep around..."
So what I mean is: how much performance are we giving up with this "fix" for qsort?
- anonymoushn 3y agothe glibc qsort function is already something you only use if you don't care about performance.
- sureglymop 3y agoThen what is a better alternative? I was always told that I shouldn't implement something as trivial as sorting algorithms by myself...
- tokedo 3y agoA simple solution is to create a C++ file and exposing sorting functions to C. E.g. "void sort_int(int *data, size_t n)". The implementation uses then std::sort. Unfortunately, qsort is really slow and sometimes barely usable.
- CyberDildonics 3y agoYou were told correctly, but there is a lot of room between using the C standard library and making your own sort. C++ STL std::sort is one, but the internet is filled with libraries you can download, of course you can find a better alternative with a search.
- SAI_Peregrinus 3y agoARM Morello does that check in hardware.