From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Gabriel Smith <ga29smith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>,
devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] dtc: Fix memory leak in character literal parsing
Date: Mon, 12 Dec 2016 10:34:52 +1100 [thread overview]
Message-ID: <20161211233452.GB12127@umbus.fritz.box> (raw)
In-Reply-To: <1481487196-20830-1-git-send-email-ga29smith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
On Sun, Dec 11, 2016 at 03:13:16PM -0500, Gabriel Smith wrote:
> The data struct used for parsing character literals was never freed
> resulting in a few bytes leaked for every character.
>
> Signed-off-by: Gabriel Smith <ga29smith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Nice catch. Merged and pushed.
> ---
> dtc-lexer.l | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/dtc-lexer.l b/dtc-lexer.l
> index 790fbf6..f252ab9 100644
> --- a/dtc-lexer.l
> +++ b/dtc-lexer.l
> @@ -184,16 +184,16 @@ static void lexical_error(const char *fmt, ...);
> if (d.len == 1) {
> lexical_error("Empty character literal");
> yylval.integer = 0;
> - return DT_CHAR_LITERAL;
> - }
> -
> - yylval.integer = (unsigned char)d.val[0];
> + } else {
> + yylval.integer = (unsigned char)d.val[0];
>
> - if (d.len > 2)
> - lexical_error("Character literal has %d"
> - " characters instead of 1",
> - d.len - 1);
> + if (d.len > 2)
> + lexical_error("Character literal has %d"
> + " characters instead of 1",
> + d.len - 1);
> + }
>
> + data_free(d);
> return DT_CHAR_LITERAL;
> }
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-12-11 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 20:13 [PATCH] dtc: Fix memory leak in character literal parsing Gabriel Smith
[not found] ` <1481487196-20830-1-git-send-email-ga29smith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-11 23:34 ` David Gibson [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=20161211233452.GB12127@umbus.fritz.box \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ga29smith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jdl-CYoMK+44s/E@public.gmane.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;
as well as URLs for NNTP newsgroup(s).