From: Andrea Claudi <aclaudi@redhat.com>
To: netdev@vger.kernel.org
Cc: stephen@networkplumber.org, dsahern@gmail.com,
markzhang@nvidia.com, leonro@nvidia.com
Subject: [PATCH iproute2 0/3] some memory leak fixes
Date: Tue, 1 Feb 2022 18:39:23 +0100 [thread overview]
Message-ID: <cover.1643736038.git.aclaudi@redhat.com> (raw)
This series fixes some memory leaks related to the usage of the
get_task_name() function from lib/fs.c.
Patch 3/3 addresses a coverity warning related to this memory leak,
making the code a bit more readable by humans and coverity.
Andrea Claudi (3):
lib/fs: fix memory leak in get_task_name()
rdma: stat: fix memory leak in res_counter_line()
rdma: RES_PID and RES_KERN_NAME are alternatives to each other
lib/fs.c | 10 +++++--
rdma/res-cmid.c | 10 +++----
rdma/res-cq.c | 9 +++---
rdma/res-ctx.c | 9 +++---
rdma/res-mr.c | 8 ++---
rdma/res-pd.c | 9 +++---
rdma/res-qp.c | 9 +++---
rdma/res-srq.c | 10 +++----
rdma/stat.c | 79 ++++++++++++++++++++++++++++++++-----------------
9 files changed, 88 insertions(+), 65 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-01 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 17:39 Andrea Claudi [this message]
2022-02-01 17:39 ` [PATCH iproute2 1/3] lib/fs: fix memory leak in get_task_name() Andrea Claudi
2022-02-01 18:27 ` Stephen Hemminger
2022-02-02 14:38 ` Andrea Claudi
2022-02-02 15:49 ` Stephen Hemminger
2022-02-01 17:39 ` [PATCH iproute2 2/3] rdma: stat: fix memory leak in res_counter_line() Andrea Claudi
2022-02-01 17:39 ` [PATCH iproute2 3/3] rdma: RES_PID and RES_KERN_NAME are alternatives to each other Andrea Claudi
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.1643736038.git.aclaudi@redhat.com \
--to=aclaudi@redhat.com \
--cc=dsahern@gmail.com \
--cc=leonro@nvidia.com \
--cc=markzhang@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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.