All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Guanqin Miao <miaoguanqin@huawei.com>
Cc: <jes@trained-monkey.org>, <pmenzel@molgen.mpg.de>,
	<linux-raid@vger.kernel.org>, <linfeilong@huawei.com>,
	<lixiaokeng@huawei.com>, <louhongxiang@huawei.com>
Subject: Re: [PATCH 1/4] Fix memory leak in file Assemble
Date: Wed, 23 Aug 2023 15:43:01 +0200	[thread overview]
Message-ID: <20230823154301.00006d16@linux.intel.com> (raw)
In-Reply-To: <20230424080637.2152893-2-miaoguanqin@huawei.com>

On Mon, 24 Apr 2023 16:06:34 +0800
Guanqin Miao <miaoguanqin@huawei.com> wrote:

> When we test mdadm with asan, we found some memory leaks in Assemble.c
> We fix these memory leaks based on code logic.
> 
> Signed-off-by: Guanqin Miao <miaoguanqin@huawei.com>
> Signed-off-by: Li Xiao Keng <lixiaokeng@huawei.com>
> ---

Acked-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>

  reply	other threads:[~2023-08-23 13:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24  8:06 [PATCH 0/4] Fix memory leak for Manage Assemble Kill mdadm Guanqin Miao
2023-04-24  8:06 ` [PATCH 1/4] Fix memory leak in file Assemble Guanqin Miao
2023-08-23 13:43   ` Mariusz Tkaczyk [this message]
2023-04-24  8:06 ` [PATCH 2/4] Fix memory leak in file Kill Guanqin Miao
2023-08-23 13:49   ` Mariusz Tkaczyk
2023-04-24  8:06 ` [PATCH 3/4] Fix memory leak in file Manage Guanqin Miao
2023-08-23 13:50   ` Mariusz Tkaczyk
2023-04-24  8:06 ` [PATCH 4/4] Fix memory leak in file mdadm Guanqin Miao
2023-08-23 13:51   ` Mariusz Tkaczyk
2023-09-01 16:02 ` [PATCH 0/4] Fix memory leak for Manage Assemble Kill mdadm Jes Sorensen
2023-09-01 16:07   ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2023-04-06 11:40 Guanqin Miao
2023-04-06 11:40 ` [PATCH 1/4] Fix memory leak in file Assemble Guanqin Miao
2023-04-10 15:54   ` Jes Sorensen
2023-03-23  1:30 [PATCH 0/4] Fix memory leak for Manage Assemble Kill mdadm miaoguanqin
2023-03-23  1:30 ` [PATCH 1/4] Fix memory leak in file Assemble miaoguanqin
2023-03-28  7:54   ` Mariusz Tkaczyk
2023-03-28 11:21   ` Paul Menzel

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=20230823154301.00006d16@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=jes@trained-monkey.org \
    --cc=linfeilong@huawei.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lixiaokeng@huawei.com \
    --cc=louhongxiang@huawei.com \
    --cc=miaoguanqin@huawei.com \
    --cc=pmenzel@molgen.mpg.de \
    /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.