All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Edwin Török" <edvin.torok@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: "Edwin Török" <edwin.torok@cloud.com>, "Wei Liu" <wl@xen.org>,
	"Anthony PERARD" <anthony.perard@citrix.com>,
	"Juergen Gross" <jgross@suse.com>
Subject: [PATCH v1 0/2] fix memory leaks reported by GCC -fanalyzer
Date: Fri, 24 Feb 2023 13:36:44 +0000	[thread overview]
Message-ID: <cover.1677245356.git.edwin.torok@cloud.com> (raw)

From: Edwin Török <edwin.torok@cloud.com>

Using GCC 12.2.1 with -fanalyzer it has shown some memory leaks:

This is how I enabled -fanalyzer (adding it to CFLAGS for toplevel
configure didn't seem to work):

```
CFLAGS += $(call cc-option,$(CC),-fanalyzer)
```

Note that there are more errors shown than fixed here, but they seem to
be false positives (which is why this flag cannot, yet, be enabled by
default).

Edwin Török (2):
  xc_core_arch_map_p2m_tree_rw: fix memory leak
  backup_ptes: fix leak on realloc failure

 tools/libs/guest/xg_core_x86.c     | 2 ++
 tools/libs/guest/xg_offline_page.c | 7 +++++--
 2 files changed, 7 insertions(+), 2 deletions(-)

-- 
2.39.1



             reply	other threads:[~2023-02-24 13:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 13:36 Edwin Török [this message]
2023-02-24 13:36 ` [PATCH v1 1/2] xc_core_arch_map_p2m_tree_rw: fix memory leak Edwin Török
2023-02-24 14:56   ` Andrew Cooper
2023-02-27 10:36     ` Edwin Torok
2023-02-27 14:42     ` Juergen Gross
2023-02-27 14:49       ` Andrew Cooper
2023-02-27 15:00   ` [PATCH] libs/guest: Fix resource leaks in xc_core_arch_map_p2m_tree_rw() Andrew Cooper
2023-02-24 13:36 ` [PATCH v1 2/2] backup_ptes: fix leak on realloc failure Edwin Török
2023-02-24 15:00   ` Andrew Cooper

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=cover.1677245356.git.edwin.torok@cloud.com \
    --to=edvin.torok@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=edwin.torok@cloud.com \
    --cc=jgross@suse.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.