summaryrefslogtreecommitdiff
path: root/Documentation/technical/protocol-capabilities.txt
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2017-09-05 08:15:21 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-09-06 17:19:54 +0900
commitbfffb48c5d520a5f181716b0330774a03cd3fa39 (patch)
tree78488ee47fe26a6f3c1592c69402ba36f7661792 /Documentation/technical/protocol-capabilities.txt
parentref_lock: stop leaking lock_files (diff)
downloadtgif-bfffb48c5d520a5f181716b0330774a03cd3fa39.tar.xz
stop leaking lock structs in some simple cases
Now that it's safe to declare a "struct lock_file" on the stack, we can do so (and avoid an intentional leak). These leaks were found by running t0000 and t0001 under valgrind (though certainly other similar leaks exist and just don't happen to be exercised by those tests). Initializing the lock_file's inner tempfile with NULL is not strictly necessary in these cases, but it's a good practice to model. It means that if we were to call a function like rollback_lock_file() on a lock that was never taken in the first place, it becomes a quiet noop (rather than undefined behavior). Likewise, it's always safe to rollback_lock_file() on a file that has already been committed or deleted, since that operation is a noop on an inactive lockfile (and that's why the case in config.c can drop the "if (lock)" check as we move away from using a pointer). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/technical/protocol-capabilities.txt')
0 files changed, 0 insertions, 0 deletions