diff options
author | René Scharfe <l.s.r@web.de> | 2019-11-12 22:41:34 +0100 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2019-11-13 11:44:00 +0900 |
commit | 169bed7421b9c71870231e41ccb93a7abad3240e (patch) | |
tree | 040c53ec3750405a753c9fe2bae50af5d852cf9b /Documentation | |
parent | Git 2.23 (diff) | |
download | tgif-169bed7421b9c71870231e41ccb93a7abad3240e.tar.xz |
parse-options: avoid arithmetic on pointer that's potentially NULL
parse_options_dup() counts the number of elements in the given array
without the end marker, allocates enough memory to hold all of them plus
an end marker, then copies them and terminates the new array. The
counting part is done by advancing a pointer through the array, and the
original pointer is reconstructed using pointer subtraction before the
copy operation.
The function is also prepared to handle a NULL pointer passed to it.
None of its callers do that currently, but this feature was used by
46e91b663b ("checkout: split part of it to new command 'restore'",
2019-04-25); it seems worth keeping.
It ends up doing arithmetic on that NULL pointer, though, which is
undefined in standard C, when it tries to calculate "NULL - 0". Better
avoid doing that by remembering the originally given pointer value.
There is another issue, though. memcpy(3) does not support NULL
pointers, even for empty arrays. Use COPY_ARRAY instead, which does
support such empty arrays. Its call is also shorter and safer by
inferring the element type automatically.
Coccinelle and contrib/coccinelle/array.cocci did not propose to use
COPY_ARRAY because of the pointer subtraction and because the source is
const -- the semantic patch cautiously only considers pointers and array
references of the same type.
Signed-off-by: René Scharfe <l.s.r@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions