diff options
author | Vegard Nossum <vegard.nossum@oracle.com> | 2017-03-05 06:44:46 -0500 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2017-03-06 12:01:02 -0800 |
commit | 07f546cda5d818780821a371f011eb253646ddc3 (patch) | |
tree | 2619b0a6e9a6724c3b45e53621396c3b6c70833c /t/t5100 | |
parent | preparing for 2.10.3 (diff) | |
download | tgif-07f546cda5d818780821a371f011eb253646ddc3.tar.xz |
line-log: use COPY_ARRAY to fix mis-sized memcpy
This memcpy meant to get the sizeof a "struct range", not a
"range_set", as the former is what our array holds. Rather
than swap out the types, let's convert this site to
COPY_ARRAY, which avoids the problem entirely (and confirms
that the src and dst types match).
Note for curiosity's sake that this bug doesn't trigger on
I32LP64 systems, but does on ILP32 systems. The mistaken
"struct range_set" has two ints and a pointer. That's 16
bytes on LP64, or 12 on ILP32. The correct "struct range"
type has two longs, which is also 16 on LP64, but only 8 on
ILP32.
Likewise an IL32P64 system would experience the bug.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5100')
0 files changed, 0 insertions, 0 deletions