From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH] linux-user: fix resource leaks in gen-vdso
Date: Thu, 20 Mar 2025 17:38:33 +0000 [thread overview]
Message-ID: <Z9xSmaaZI_dJnXKM@redhat.com> (raw)
In-Reply-To: <20250219100336.1696758-1-berrange@redhat.com>
ping, any thoughts on this patch
On Wed, Feb 19, 2025 at 10:03:36AM +0000, Daniel P. Berrangé wrote:
> There are a number of resource leaks in gen-vdso. In theory they are
> harmless because this is a short lived process, but when building QEMU
> with --extra-cflags="-fsanitize=address" problems ensure. The gen-vdso
> program is run as part of the build, and that aborts due to the
> sanitizer identifying memory leaks, leaving QEMU unbuildable.
>
> FAILED: libqemu-x86_64-linux-user.a.p/vdso.c.inc
> /var/home/berrange/src/virt/qemu/build/linux-user/gen-vdso -o libqemu-x86_64-linux-user.a.p/vdso.c.inc ../linux-user/x86_64/vdso.so
>
> =================================================================
> ==1696332==ERROR: LeakSanitizer: detected memory leaks
>
> Direct leak of 2968 byte(s) in 1 object(s) allocated from:
> #0 0x56495873f1f3 (/var/home/berrange/src/virt/qemu/build/linux-user/gen-vdso+0xa11f3) (BuildId: b69e241ad44719b6f3934f3c71dfc6727e8bdb12)
> #1 0x564958780b90 (/var/home/berrange/src/virt/qemu/build/linux-user/gen-vdso+0xe2b90) (BuildId: b69e241ad44719b6f3934f3c71dfc6727e8bdb12)
>
> This complaint is about the 'buf' variable, however, the FILE objects
> are also leaked in some error scenarios, so this fix refactors the
> cleanup paths to fix all leaks. For completeness it also reports an
> error if fclose() fails on 'inf'.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> linux-user/gen-vdso.c | 29 +++++++++++++++++------------
> 1 file changed, 17 insertions(+), 12 deletions(-)
>
> diff --git a/linux-user/gen-vdso.c b/linux-user/gen-vdso.c
> index 721f38d5a3..88d94b19eb 100644
> --- a/linux-user/gen-vdso.c
> +++ b/linux-user/gen-vdso.c
> @@ -56,13 +56,14 @@ static unsigned rt_sigreturn_addr;
>
> int main(int argc, char **argv)
> {
> - FILE *inf, *outf;
> + FILE *inf = NULL, *outf = NULL;
> long total_len;
> const char *prefix = "vdso";
> const char *inf_name;
> const char *outf_name = NULL;
> - unsigned char *buf;
> + unsigned char *buf = NULL;
> bool need_bswap;
> + int ret = EXIT_FAILURE;
>
> while (1) {
> int opt = getopt(argc, argv, "o:p:r:s:");
> @@ -129,7 +130,6 @@ int main(int argc, char **argv)
> fprintf(stderr, "%s: incomplete read\n", inf_name);
> return EXIT_FAILURE;
> }
> - fclose(inf);
>
> /*
> * Identify which elf flavor we're processing.
> @@ -205,19 +205,24 @@ int main(int argc, char **argv)
> fprintf(outf, " .rt_sigreturn_ofs = 0x%x,\n", rt_sigreturn_addr);
> fprintf(outf, "};\n");
>
> - /*
> - * Everything should have gone well.
> - */
> - if (fclose(outf)) {
> - goto perror_outf;
> - }
> - return EXIT_SUCCESS;
> + ret = EXIT_SUCCESS;
> +
> + cleanup:
> + free(buf);
> +
> + if (outf &&
> + fclose(outf) != 0)
> + ret = EXIT_FAILURE;
> + if (inf &&
> + fclose(inf) != 0)
> + ret = EXIT_FAILURE;
> + return ret;
>
> perror_inf:
> perror(inf_name);
> - return EXIT_FAILURE;
> + goto cleanup;
>
> perror_outf:
> perror(outf_name);
> - return EXIT_FAILURE;
> + goto cleanup;
> }
> --
> 2.47.1
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-03-20 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 10:03 [PATCH] linux-user: fix resource leaks in gen-vdso Daniel P. Berrangé
2025-03-20 17:38 ` Daniel P. Berrangé [this message]
2025-03-20 23:16 ` Richard Henderson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z9xSmaaZI_dJnXKM@redhat.com \
--to=berrange@redhat.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
/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.
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 NNTP newsgroup(s).