From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Jean-Christophe DUBOIS <jcd-WBS85hRCVJbxB9160cZjhg@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jdl-CYoMK+44s/E@public.gmane.org
Subject: Re: [PATCH] fdtget.c: Fix memory leak
Date: Sun, 24 Jul 2016 01:04:30 +1000 [thread overview]
Message-ID: <20160723150430.GD24621@voom.fritz.box> (raw)
In-Reply-To: <5785DA1C.7030601-WBS85hRCVJbxB9160cZjhg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2181 bytes --]
On Wed, Jul 13, 2016 at 08:05:16AM +0200, Jean-Christophe DUBOIS wrote:
> Le 13/07/2016 04:50, David Gibson a écrit :
> > On Wed, Jul 13, 2016 at 12:36:08AM +0200, Jean-Christophe Dubois wrote:
> > > CID 132823 (#1 of 1): Resource leak (RESOURCE_LEAK)
> > > 5. leaked_storage: Variable blob going out of scope leaks the storage it points to.
> > >
> > > Signed-off-by: Jean-Christophe Dubois <jcd-WBS85hRCVJbxB9160cZjhg@public.gmane.org>
> > Since the program exits immediately after this free(), there's really
> > no point.
> This is usually a good practice to free explicitly the memory we are
> allocating rather than relying on some kind of (final) garbage collector
> (like in java).
Well... it's important to have a consistent model for memory
management and stick to it. For little programs like this, never
freeing - essentially using the process lifetime as a really simple
pool allocator - is a pretty valid option.
That said, I guess there are existing free()s so it's not really using
that model consistently. So, yeah, ok, we might as well shut the
checker up by applying these.
>
> It seems cheap to fix but this is your call.
> >
> > > ---
> > > fdtget.c | 8 +++++++-
> > > 1 file changed, 7 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/fdtget.c b/fdtget.c
> > > index 4377419..fb9d0e1 100644
> > > --- a/fdtget.c
> > > +++ b/fdtget.c
> > > @@ -266,14 +266,20 @@ static int do_fdtget(struct display_info *disp, const char *filename,
> > > continue;
> > > } else {
> > > report_error(arg[i], node);
> > > + free(blob);
> > > return -1;
> > > }
> > > }
> > > prop = args_per_step == 1 ? NULL : arg[i + 1];
> > > - if (show_data_for_item(blob, disp, node, prop))
> > > + if (show_data_for_item(blob, disp, node, prop)) {
> > > + free(blob);
> > > return -1;
> > > + }
> > > }
> > > +
> > > + free(blob);
> > > +
> > > return 0;
> > > }
>
--
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-07-23 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 22:36 [PATCH] fdtget.c: Fix memory leak Jean-Christophe Dubois
[not found] ` <1468362968-32090-1-git-send-email-jcd-WBS85hRCVJbxB9160cZjhg@public.gmane.org>
2016-07-13 2:50 ` David Gibson
[not found] ` <20160713025005.GD14615-RXTfZT5YzpxwFLYp8hBm2A@public.gmane.org>
2016-07-13 6:05 ` Jean-Christophe DUBOIS
[not found] ` <5785DA1C.7030601-WBS85hRCVJbxB9160cZjhg@public.gmane.org>
2016-07-23 15:04 ` 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=20160723150430.GD24621@voom.fritz.box \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jcd-WBS85hRCVJbxB9160cZjhg@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).