From: Wu Guanghao <wuguanghao3@huawei.com>
To: <jes@trained-monkey.org>, <linux-raid@vger.kernel.org>
Cc: <linfeilong@huawei.com>, <lixiaokeng@huawei.com>
Subject: [PATCH 0/5] mdadm: fix memory leak and double free
Date: Tue, 31 May 2022 14:48:44 +0800 [thread overview]
Message-ID: <00992179-9572-ceb4-eb49-492c42e67695@huawei.com> (raw)
Through tool scanning and code review, we found several memory leaks and double free
Wu Guanghao (5):
parse_layout_faulty: fix memleak
Detail: fix memleak
load_imsm_mpb: fix double free
find_disk_attached_hba: fix memleak
get_vd_num_of_subarray: fix memleak
Detail.c | 1 +
super-ddf.c | 9 +++++++--
super-intel.c | 6 ++++--
util.c | 1 +
4 files changed, 13 insertions(+), 4 deletions(-)
--
2.27.0
next reply other threads:[~2022-05-31 6:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 6:48 Wu Guanghao [this message]
2022-05-31 6:49 ` [PATCH 1/5] parse_layout_faulty: fix memleak Wu Guanghao
2022-05-31 7:36 ` Mariusz Tkaczyk
2022-06-07 7:24 ` Wu Guanghao
2022-05-31 6:49 ` [PATCH 2/5] Detail: " Wu Guanghao
2022-05-31 7:42 ` Mariusz Tkaczyk
2022-05-31 6:50 ` [PATCH 3/5] load_imsm_mpb: fix double free Wu Guanghao
2022-05-31 7:54 ` Mariusz Tkaczyk
2022-05-31 6:50 ` [PATCH 4/5] find_disk_attached_hba: fix memleak Wu Guanghao
2022-05-31 8:04 ` Mariusz Tkaczyk
2022-06-07 7:36 ` Wu Guanghao
2022-05-31 6:51 ` [PATCH 5/5] get_vd_num_of_subarray: " Wu Guanghao
2022-05-31 8:11 ` Mariusz Tkaczyk
2022-05-31 8:25 ` Paul Menzel
2022-06-07 6:32 ` Mariusz Tkaczyk
2022-05-31 6:57 ` [PATCH 0/5] mdadm: fix memory leak and double free Paul Menzel
2022-06-07 7:39 ` Wu Guanghao
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=00992179-9572-ceb4-eb49-492c42e67695@huawei.com \
--to=wuguanghao3@huawei.com \
--cc=jes@trained-monkey.org \
--cc=linfeilong@huawei.com \
--cc=linux-raid@vger.kernel.org \
--cc=lixiaokeng@huawei.com \
/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.