mirror of
git://sourceware.org/git/glibc.git
synced 2024-12-09 04:11:27 +08:00
c044cf14b0
Wrong copy algorithm for last bytes, not thread safety. In some particular cases it uses the destination memory beyond the string end for 16-byte load, puts changes into that part that is relevant to destination string and writes whole 16-byte chunk into memory. I have a test case where the memory beyond the string end contains malloc/free data, that appear corrupted in case free() updates it in between the 16-byte read and 16-byte write. |
||
---|---|---|
.. | ||
fpu | ||
multiarch | ||
add_n.S | ||
bcopy.S | ||
bzero.S | ||
cacheinfo.c | ||
dl-hash.h | ||
ffs.c | ||
hp-timing.c | ||
hp-timing.h | ||
Implies | ||
Makefile | ||
memcmp.S | ||
memcpy_chk.S | ||
memcpy.S | ||
memmove_chk.S | ||
memmove.S | ||
mempcpy_chk.S | ||
mempcpy.S | ||
memset_chk.S | ||
memset.S | ||
memusage.h | ||
strcmp.S | ||
strtok_r.S | ||
strtok.S | ||
tst-stack-align.h |