From: Simon Horman <horms@verge.net.au>
To: qiuguorui1 <qiuguorui1@huawei.com>
Cc: yszhou4tech@gmail.com, leeyou.li@huawei.com,
kexec@lists.infradead.org, zengweilin@huawei.com
Subject: Re: [PATCH] zlib: fix resource leak when gzdirect failed
Date: Mon, 30 Nov 2020 17:37:31 +0100 [thread overview]
Message-ID: <20201130163731.GB20208@vergenet.net> (raw)
In-Reply-To: <20201130064125.1379-1-qiuguorui1@huawei.com>
On Mon, Nov 30, 2020 at 02:41:25PM +0800, qiuguorui1 wrote:
> In function zlib_decompress_file, when gzdirect(fp) fails,
> we should gzclose fp before return.
>
> Fixes: d606837b56d46 ("Fix zlib/lzma decompression.")
> Signed-off-by: qiuguorui1 <qiuguorui1@huawei.com>
Thanks, applied.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2020-11-30 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 6:41 [PATCH] zlib: fix resource leak when gzdirect failed qiuguorui1
2020-11-30 16:37 ` Simon Horman [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=20201130163731.GB20208@vergenet.net \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=leeyou.li@huawei.com \
--cc=qiuguorui1@huawei.com \
--cc=yszhou4tech@gmail.com \
--cc=zengweilin@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