From: Chao Yu <chao@kernel.org>
To: Maxim Korotkov <korotkov.maxim.s@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] fsck.f2fs: fix memleak in f2fs_create()
Date: Mon, 5 Jun 2023 14:18:21 +0800 [thread overview]
Message-ID: <dfaa57a4-494b-76ba-b181-bf0add5e1c3b@kernel.org> (raw)
In-Reply-To: <20230605060853.679169-1-korotkov.maxim.s@gmail.com>
On 2023/6/5 14:08, Maxim Korotkov wrote:
> In error handling cases, exiting a function without releasing memory
>
> Signed-off-by: Maxim Korotkov <korotkov.maxim.s@gmail.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2023-06-05 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 6:08 [f2fs-dev] [PATCH v3] fsck.f2fs: fix memleak in f2fs_create() Maxim Korotkov
2023-06-05 6:18 ` Chao Yu [this message]
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=dfaa57a4-494b-76ba-b181-bf0add5e1c3b@kernel.org \
--to=chao@kernel.org \
--cc=korotkov.maxim.s@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).