From: Coly Li <colyli@suse.de>
To: Zhiqiang Liu <liuzhiqiang26@huawei.com>
Cc: linfeilong <linfeilong@huawei.com>,
lixiaokeng <lixiaokeng@huawei.com>,
linux-bcache@vger.kernel.org
Subject: Re: [PATCH] bcache-tools: fix potential memoryleak problem in, may_add_item()
Date: Tue, 2 Mar 2021 21:33:37 +0800 [thread overview]
Message-ID: <9e68d3fe-52bc-a496-5cad-ec47c1d295c1@suse.de> (raw)
In-Reply-To: <c475bf5f-d284-aea9-5898-6ef3581138fb@huawei.com>
On 2/27/21 10:38 AM, Zhiqiang Liu wrote:
>
> In may_add_item(), it will directly return 1 without freeing
> variable tmp and closing fd, when the return value of detail_base()
> is not equal to 0. In addition, we do not check whether
> allocating memory for tmp is successful.
>
> Here, we will check whether malloc() returns NULL, and
> will free tmp and close fd when detail_base() fails.
>
> Signed-off-by: ZhiqiangLiu <lzhq28@mail.ustc.edu.cn>
Applied. BTW, I change your above name string from ZhiqiangLiu to
Zhiqiang Liu, because of the checkpatch.pl warning.
Thanks.
Coly Li
> ---
> lib.c | 28 +++++++++++++++++-----------
> 1 file changed, 17 insertions(+), 11 deletions(-)
>
> diff --git a/lib.c b/lib.c
> index 6341c61..745dab6 100644
> --- a/lib.c
> +++ b/lib.c
> @@ -382,7 +382,7 @@ int may_add_item(char *devname, struct list_head *head)
> struct cache_sb sb;
> char dev[512];
> struct dev *tmp;
> - int ret;
> + int ret = 0;
>
> if (strcmp(devname, ".") == 0 || strcmp(devname, "..") == 0)
> return 0;
> @@ -392,27 +392,33 @@ int may_add_item(char *devname, struct list_head *head)
> if (fd == -1)
> return 0;
>
> - if (pread(fd, &sb_disk, sizeof(sb_disk), SB_START) != sizeof(sb_disk)) {
> - close(fd);
> - return 0;
> - }
> + if (pread(fd, &sb_disk, sizeof(sb_disk), SB_START) != sizeof(sb_disk))
> + goto out;
>
> - if (memcmp(sb_disk.magic, bcache_magic, 16)) {
> - close(fd);
> - return 0;
> - }
> + if (memcmp(sb_disk.magic, bcache_magic, 16))
> + goto out;
>
> to_cache_sb(&sb, &sb_disk);
>
> tmp = (struct dev *) malloc(DEVLEN);
> + if (tmp == NULL) {
> + fprintf(stderr, "Error: fail to allocate memory buffer\n");
> + ret = 1;
> + goto out;
> + }
> +
> tmp->csum = le64_to_cpu(sb_disk.csum);
> ret = detail_base(dev, sb, tmp);
> if (ret != 0) {
> fprintf(stderr, "Failed to get information for %s\n", dev);
> - return 1;
> + free(tmp);
> + goto out;
> }
> list_add_tail(&tmp->dev_list, head);
> - return 0;
> +
> +out:
> + close(fd);
> + return ret;
> }
>
> int list_bdevs(struct list_head *head)
>
next prev parent reply other threads:[~2021-03-03 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 2:38 [PATCH] bcache-tools: fix potential memoryleak problem in, may_add_item() Zhiqiang Liu
2021-03-02 13:33 ` Coly Li [this message]
2021-03-03 0:50 ` Zhiqiang Liu
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=9e68d3fe-52bc-a496-5cad-ec47c1d295c1@suse.de \
--to=colyli@suse.de \
--cc=linfeilong@huawei.com \
--cc=linux-bcache@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--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 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).