public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <timothy.shimmin@gmail.com>
To: Zdenek Prikryl <zprikryl@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: libattr - severe memory leaks from attr_copy_file()
Date: Fri, 20 Feb 2009 11:33:13 +1100	[thread overview]
Message-ID: <d38e348a0902191633x382e4683scfdc3f07b2f9be03@mail.gmail.com> (raw)
In-Reply-To: <499D0471.6000600@redhat.com>

Hi Zdenek,

On Thu, Feb 19, 2009 at 6:04 PM, Zdenek Prikryl <zprikryl@redhat.com> wrote:
>> And the variable, text, is assigned straight away before any use,
>> so I missed where the problem is.
>>
>> --Tim
>
> The memory leak is really there. Look:
:-)

>
> 54 attr_parse_attr_conf(struct error_context *ctx)
> ...
> 66 repeat:
> 67         text = malloc(size_guess + 1);
> 68         if (!text)
> 69                 goto fail;
> 70
> 71         if ((file = fopen(ATTR_CONF, "r")) == NULL) {
> 72                 if (errno == ENOENT)
> 73                         return 0;
> 74                 goto fail;
> 75         }
>
> Let's say that malloc() on the line 67 success, so we have text != NULL. Then,
> fopen() on the line 71 fails and errno == ENOENT. In that case
> attr_parse_attr_conf() simply returns 0, but text isn't freed. That's the point,
> where memory leaks arise. I rewrote the patch, so now is more simpler.
>
Oh okay.
I see. I was looking at the "fail" case.
Hmmm.... the direct return case.
The simpler patch looks better - cool.

So I now worry about all the cases where we call return directly.
It looks like the code is building up an action list and string dup'ing
patterns.
So in the normal case where it processes them and then returns 0,
I can't see where it is free'ing the text.
Am I missing something again?

My other concern is the free(pattern) and the free(attr_actions->pattern)
with the possibility of trying to free the pattern twice. Probably, could set
pattern to NULL after it is put into the new action or some such.

--Tim


> --
> Zdenek Prikryl <zprikryl@redhat.com>
>
>
> diff -up attr-2.4.43/libattr/attr_copy_action.c.leak attr-2.4.43/libattr/attr_copy_action.c
> --- attr-2.4.43/libattr/attr_copy_action.c.leak 2008-06-30 07:22:50.000000000 +0200
> +++ attr-2.4.43/libattr/attr_copy_action.c      2009-02-17 09:50:38.000000000 +0100
> @@ -53,7 +53,7 @@ free_attr_actions(void)
>  static int
>  attr_parse_attr_conf(struct error_context *ctx)
>  {
> -       char *text, *t;
> +       char *text = NULL, *t;
>        size_t size_guess = 4096, len;
>        FILE *file;
>        char *pattern = NULL;
> @@ -64,15 +64,16 @@ attr_parse_attr_conf(struct error_contex
>                return 0;
>
>  repeat:
> -       text = malloc(size_guess + 1);
> -       if (!text)
> -               goto fail;
> -
>        if ((file = fopen(ATTR_CONF, "r")) == NULL) {
>                if (errno == ENOENT)
>                        return 0;
>                goto fail;
>        }
> +
> +       text = malloc(size_guess + 1);
> +       if (!text)
> +               goto fail;
> +
>        len = fread(text, 1, size_guess, file);
>        if (ferror(file))
>                goto fail;
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
>

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2009-02-20  0:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19  7:04 libattr - severe memory leaks from attr_copy_file() Zdenek Prikryl
2009-02-19 16:31 ` Eric Sandeen
2009-02-20  0:33 ` Timothy Shimmin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-17 11:50 Zdenek Prikryl
2009-02-17 12:04 ` Arkadiusz Miskiewicz
2009-02-18  7:08   ` Timothy Shimmin

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=d38e348a0902191633x382e4683scfdc3f07b2f9be03@mail.gmail.com \
    --to=timothy.shimmin@gmail.com \
    --cc=xfs@oss.sgi.com \
    --cc=zprikryl@redhat.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