From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: Josh Law <hlcj1234567@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Josh Law <objecting@objecting.org>
Subject: Re: [PATCH] lib/inflate: fix memory leak in inflate_dynamic() on inflate_codes() failure
Date: Sun, 8 Mar 2026 01:11:58 +0800 [thread overview]
Message-ID: <aaxcXnhITg4OIvhN@google.com> (raw)
In-Reply-To: <20260306161647.2811874-1-objecting@objecting.org>
Hi Josh,
On Fri, Mar 06, 2026 at 04:16:47PM +0000, Josh Law wrote:
> When inflate_codes() fails in inflate_dynamic(), the code jumps to the
> 'out' label which only frees 'll', leaking the Huffman tables 'tl' and
> 'td'. Restructure the code so that the decoding tables are always freed
> before reaching the 'out' label.
>
> Signed-off-by: Josh Law <objecting@objecting.org>
The change itself looks good.
However, IIRC, this isn't the first time I've complained about the
following checkpatch.pl warning:
WARNING: From:/Signed-off-by: email address mismatch: 'From: Josh Law <hlcj1234567@gmail.com>' != 'Signed-off-by: Josh Law <objecting@objecting.org>'
Regards,
Kuan-Wei
> ---
> lib/inflate.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/lib/inflate.c b/lib/inflate.c
> index 5b1e70d0ce8c..ae704e4f64ec 100644
> --- a/lib/inflate.c
> +++ b/lib/inflate.c
> @@ -1009,10 +1009,10 @@ DEBG("dyn5d ");
> DEBG("dyn6 ");
>
> /* decompress until an end-of-block code */
> - if (inflate_codes(tl, td, bl, bd)) {
> + if (inflate_codes(tl, td, bl, bd))
> ret = 1;
> - goto out;
> - }
> + else
> + ret = 0;
>
> DEBG("dyn7 ");
>
> @@ -1021,7 +1021,6 @@ DEBG("dyn7 ");
> huft_free(td);
>
> DEBG(">");
> - ret = 0;
> out:
> free(ll);
> return ret;
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2026-03-07 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 16:16 Josh Law
2026-03-07 17:11 ` Kuan-Wei Chiu [this message]
2026-03-07 17:30 ` Josh Law
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=aaxcXnhITg4OIvhN@google.com \
--to=visitorckw@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hlcj1234567@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=objecting@objecting.org \
/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
Powered by JetHome