From: Derrick Stolee <stolee@gmail.com>
To: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] stop calling UNLEAK() before die()
Date: Thu, 13 Aug 2020 14:08:45 -0400 [thread overview]
Message-ID: <275f3f6c-77ed-fddd-8f79-28f25b257362@gmail.com> (raw)
In-Reply-To: <20200813155500.GA897132@coredump.intra.peff.net>
On 8/13/2020 11:55 AM, Jeff King wrote:
> The point of UNLEAK() is to make a reference to a variable that is about
> to go out of scope so that leak-checkers will consider it to be
> not-leaked. Doing so right before die() is therefore pointless; even
> though we are about to exit the program, the variable will still be on
> the stack and accessible to leak-checkers.
>
> These annotations aren't really hurting anything, but they clutter the
> code and set a bad example of how to use UNLEAK().
Good justification. I'll stop being a bad example ;)
Thanks,
-Stolee
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> bugreport.c | 4 +---
> midx.c | 8 ++------
> 2 files changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/bugreport.c b/bugreport.c
> index 09579e268d..7ca0fba1b8 100644
> --- a/bugreport.c
> +++ b/bugreport.c
> @@ -175,10 +175,8 @@ int cmd_main(int argc, const char **argv)
> /* fopen doesn't offer us an O_EXCL alternative, except with glibc. */
> report = open(report_path.buf, O_CREAT | O_EXCL | O_WRONLY, 0666);
>
> - if (report < 0) {
> - UNLEAK(report_path);
> + if (report < 0)
> die(_("couldn't create a new file at '%s'"), report_path.buf);
> - }
>
> if (write_in_full(report, buffer.buf, buffer.len) < 0)
> die_errno(_("unable to write to %s"), report_path.buf);
> diff --git a/midx.c b/midx.c
> index a5fb797ede..737420f157 100644
> --- a/midx.c
> +++ b/midx.c
> @@ -807,11 +807,9 @@ static int write_midx_internal(const char *object_dir, struct multi_pack_index *
> int result = 0;
>
> midx_name = get_midx_filename(object_dir);
> - if (safe_create_leading_directories(midx_name)) {
> - UNLEAK(midx_name);
> + if (safe_create_leading_directories(midx_name))
> die_errno(_("unable to create leading directories of %s"),
> midx_name);
> - }
>
> if (m)
> packs.m = m;
> @@ -1051,10 +1049,8 @@ void clear_midx_file(struct repository *r)
> r->objects->multi_pack_index = NULL;
> }
>
> - if (remove_path(midx)) {
> - UNLEAK(midx);
> + if (remove_path(midx))
> die(_("failed to clear multi-pack-index at %s"), midx);
> - }
>
> free(midx);
> }
>
next prev parent reply other threads:[~2020-08-13 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 15:54 [PATCH 0/2] UNLEAK style fixes Jeff King
2020-08-13 15:55 ` [PATCH 1/2] stop calling UNLEAK() before die() Jeff King
2020-08-13 18:08 ` Derrick Stolee [this message]
2020-08-14 10:17 ` Jeff King
2020-08-13 15:55 ` [PATCH 2/2] ls-remote: simplify UNLEAK() usage Jeff King
2020-08-13 18:11 ` Derrick Stolee
2020-08-13 19:32 ` [PATCH 0/2] UNLEAK style fixes Eric Sunshine
2020-08-14 10:34 ` Jeff King
2020-08-14 16:23 ` Eric Sunshine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=275f3f6c-77ed-fddd-8f79-28f25b257362@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).