From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PATCH ci-fix 0/8] fix various memory leaks (but not all)
Date: Tue, 1 Oct 2019 15:36:20 +0200 [thread overview]
Message-ID: <1569936988-635-1-git-send-email-pbonzini@redhat.com> (raw)
Hi all, the asan and docker-clang@ubuntu tests are failing due
to memory leaks, mostly in instance_init but some also in
realize. The former are caught by device-introspect-test,
the latter by boot-serial-test.
This series fixes the simplest ones. ARM and aarch64 failures
remain so I'm disabling LeakSanitizer tests in CI with the last
patch.
Paolo
Paolo Bonzini (8):
ide: fix leak from qemu_allocate_irqs
microblaze: fix leak of fdevice tree blob
mcf5208: fix leak from qemu_allocate_irqs
hppa: fix leak from g_strdup_printf
mips: fix memory leaks in board initialization
cris: do not leak struct cris_disasm_data
lm32: do not leak memory on object_new/object_unref
docker: test-debug: disable LeakSanitizer
disas/cris.c | 59 ++++++++++++++++++++++-----------------------
hw/hppa/dino.c | 1 +
hw/hppa/machine.c | 4 ++-
hw/ide/cmd646.c | 1 +
hw/m68k/mcf5208.c | 2 ++
hw/microblaze/boot.c | 1 +
hw/mips/mips_int.c | 1 +
hw/mips/mips_jazz.c | 2 ++
hw/timer/lm32_timer.c | 6 ++---
hw/timer/milkymist-sysctl.c | 10 ++++----
tests/docker/test-debug | 1 +
11 files changed, 49 insertions(+), 39 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-10-01 13:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 13:36 Paolo Bonzini [this message]
2019-10-01 13:36 ` [PATCH 1/8] ide: fix leak from qemu_allocate_irqs Paolo Bonzini
2019-10-01 14:25 ` Thomas Huth
2019-10-01 15:28 ` Eric Blake
2019-10-01 15:58 ` Peter Maydell
2019-10-01 16:52 ` Paolo Bonzini
2019-10-01 13:36 ` [PATCH 2/8] microblaze: fix leak of fdevice tree blob Paolo Bonzini
2019-10-01 14:01 ` Philippe Mathieu-Daudé
2019-10-01 13:36 ` [PATCH 3/8] mcf5208: fix leak from qemu_allocate_irqs Paolo Bonzini
2019-10-01 14:28 ` Thomas Huth
2019-10-01 13:36 ` [PATCH 4/8] hppa: fix leak from g_strdup_printf Paolo Bonzini
2019-10-01 13:59 ` Philippe Mathieu-Daudé
2019-10-01 13:36 ` [PATCH 5/8] mips: fix memory leaks in board initialization Paolo Bonzini
2019-10-01 14:34 ` Thomas Huth
2019-10-01 13:36 ` [PATCH 6/8] cris: do not leak struct cris_disasm_data Paolo Bonzini
2019-10-01 13:36 ` [PATCH 7/8] lm32: do not leak memory on object_new/object_unref Paolo Bonzini
2019-10-01 14:04 ` Philippe Mathieu-Daudé
2019-10-01 13:36 ` [PATCH 8/8] docker: test-debug: disable LeakSanitizer Paolo Bonzini
2019-10-01 13:59 ` Philippe Mathieu-Daudé
2019-10-01 16:53 ` Paolo Bonzini
2019-10-01 19:28 ` [PATCH ci-fix 0/8] fix various memory leaks (but not all) no-reply
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=1569936988-635-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--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).