From: Yunlong Song <yunlong.song@huawei.com>
To: jaegeuk@kernel.org, yuchao0@huawei.com, yunlong.song@huawei.com
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: [PATCH] fsck.f2fs: free node_blk to avoid memory leak
Date: Wed, 21 Sep 2016 21:01:55 +0800 [thread overview]
Message-ID: <1474462915-20999-1-git-send-email-yunlong.song@huawei.com> (raw)
Signed-off-by: Yunlong Song <yunlong.song@huawei.com>
---
fsck/fsck.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fsck/fsck.c b/fsck/fsck.c
index e2081c8..2a4df7b 100644
--- a/fsck/fsck.c
+++ b/fsck/fsck.c
@@ -1696,6 +1696,7 @@ static void fix_hard_links(struct f2fs_sb_info *sbi)
node = node->next;
free(tmp);
}
+ free(node_blk);
}
static void fix_nat_entries(struct f2fs_sb_info *sbi)
--
1.8.5.2
------------------------------------------------------------------------------
next reply other threads:[~2016-09-21 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 13:01 Yunlong Song [this message]
2016-09-22 10:52 ` [PATCH] fsck.f2fs: free node_blk to avoid memory leak Chao Yu
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=1474462915-20999-1-git-send-email-yunlong.song@huawei.com \
--to=yunlong.song@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@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).