public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH] ldconfig: Fix memory leaks
Date: Tue, 18 May 2021 09:13:43 +0530	[thread overview]
Message-ID: <c20e3862-febb-9818-bff3-3ea6cad630f9@sourceware.org> (raw)
In-Reply-To: <1ba04d0c-6b76-94e4-4c60-ad2246aa1357@linaro.org>

On 5/17/21 10:45 PM, Adhemerval Zanella wrote:
> 
> 
> On 11/05/2021 14:16, Siddhesh Poyarekar via Libc-alpha wrote:
>> Coverity discovered that paths allocated by chroot_canon are not freed
>> in a couple of routines in ldconfig.
> 
> LGTM, just a clarification about a specific change below.
> 
> As a side note, reviewing this patch I think chroot_canon can be replaced
> with realpath.

I'll post a separate patch for it.

> 
> Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
> 
>> ---
>>   elf/ldconfig.c | 23 +++++++++++++++--------
>>   1 file changed, 15 insertions(+), 8 deletions(-)
>>
>> diff --git a/elf/ldconfig.c b/elf/ldconfig.c
>> index 28ed637a29..3192aa49d9 100644
>> --- a/elf/ldconfig.c
>> +++ b/elf/ldconfig.c
>> @@ -693,8 +693,7 @@ manual_link (char *library)
>>         if (real_path == NULL)
>>   	{
>>   	  error (0, errno, _("Can't find %s"), path);
>> -	  free (path);
>> -	  return;
>> +	  goto out;
>>   	}
>>         real_library = alloca (strlen (real_path) + strlen (libname) + 2);
>>         sprintf (real_library, "%s/%s", real_path, libname);
> 
> Why do you need this since 'real_path' does not need to be freed here ?

You're right, it's unnecessary, I'll revert this hunk.

> 
>> @@ -709,16 +708,14 @@ manual_link (char *library)
>>     if (lstat64 (real_library, &stat_buf))
>>       {
>>         error (0, errno, _("Cannot lstat %s"), library);
>> -      free (path);
>> -      return;
>> +      goto out;
>>       }
>>     /* We don't want links here!  */
> 
> Ok.
> 
>>     else if (!S_ISREG (stat_buf.st_mode))
>>       {
>>         error (0, 0, _("Ignored file %s since it is not a regular file."),
>>   	     library);
>> -      free (path);
>> -      return;
>> +      goto out;
>>       }
>>   
> 
> Ok.
> 
>>     if (process_file (real_library, library, libname, &flag, &osversion,
>> @@ -726,14 +723,16 @@ manual_link (char *library)
>>       {
>>         error (0, 0, _("No link created since soname could not be found for %s"),
>>   	     library);
>> -      free (path);
>> -      return;
>> +      goto out;
>>       }
> 
> Ok.
> 
>>     if (soname == NULL)
>>       soname = implicit_soname (libname, flag);
>>     create_links (real_path, path, libname, soname);
>>     free (soname);
>> +out:
>>     free (path);
>> +  if (path != real_path)
>> +    free (real_path);
>>   }
>>   
>>   
> 
> Ok.
> 
>> @@ -920,8 +919,16 @@ search_dir (const struct dir_entry *entry)
>>   	      /* Remove stale symlinks.  */
>>   	      if (opt_link && strstr (direntry->d_name, ".so."))
>>   		unlink (real_file_name);
>> +
>> +	      if (opt_chroot)
>> +		free (target_name);
>> +
> 
> Ok, 'opt_chroot' being not null means it was allocated using chroot_canon
> instead of alloca.  No implicit checks though.

OK, fixed.


Thanks,
Siddhesh

  reply	other threads:[~2021-05-18  3:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 17:16 Siddhesh Poyarekar
2021-05-17 16:00 ` [PING][PATCH] " Siddhesh Poyarekar
2021-05-17 17:15 ` [PATCH] " Adhemerval Zanella
2021-05-18  3:43   ` Siddhesh Poyarekar [this message]
2021-05-18  4:49     ` Siddhesh Poyarekar
2021-05-18  4:52       ` Siddhesh Poyarekar
2021-05-18 13:08         ` Adhemerval Zanella
2021-05-19  4:24           ` Siddhesh Poyarekar
2021-05-19 13:54             ` Adhemerval Zanella
2021-05-19 14:03               ` Siddhesh Poyarekar
2021-05-19 14:22                 ` Adhemerval Zanella

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=c20e3862-febb-9818-bff3-3ea6cad630f9@sourceware.org \
    --to=siddhesh@sourceware.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).