tools/nolibc/string: fix memcmp() implementation
Willy Tarreau
maintainerPATCH 1/1 tools/nolibc/string: fix memcmp() implementation
From: Rasmus Villemoes <[email protected]>
The C standard says that memcmp() must treat the buffers as consisting of "unsigned chars". If char happens to be unsigned, the casts are ok, but then obviously the c1 variable can never contain a negative value. And when char is signed, the casts are wrong, and there's still a problem with using an 8-bit quantity to hold the difference, because that can range from -255 to +255.
For example, assuming char is signed, comparing two 1-byte buffers, one containing 0x00 and another 0x80, the current implementation would return -128 for both memcmp(a, b, 1) and memcmp(b, a, 1), whereas one of those should of course return something positive.
---
Paul,
please also include this patch to your series of fixes. I messed up with memcmp() making it possibly return a wrong sign depending on the distance between input bytes. It could for example affect a use case where it would be used in the same way as with qsort() (even though we do not implement qsort). I'm sending you separately a second patch to include a selftest for this one; the selftest does not need to be backported.
Thank you!
Willy
---
tools/include/nolibc/string.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
tools/include/nolibc/string.h +2 -2
@@ -19,9 +19,9 @@ static __attribute__((unused))int memcmp (const void *s1,const void *s2,size_t n) {size_t ofs =0 ; -char c1 =0 ; +int c1 =0 ; -while (ofs < n && !(c1 = ((char *)s1)[ofs] - ((char *)s2)[ofs])) { +while (ofs < n && !(c1 = ((unsigned char *)s1)[ofs] - ((unsigned char *)s2)[ofs])) { ofs++; }return c1;
Signature · 1 line
2.17.5