From: Alan Modra <amodra@bigpond.net.au>
To: msnyder@sonic.net
Cc: binutils@sourceware.org
Subject: Re: [PATCH] reloc.c, null ptr guard
Date: Thu, 26 Jul 2007 11:12:00 -0000 [thread overview]
Message-ID: <20070726093721.GE11649@bubble.grove.modra.org> (raw)
In-Reply-To: <24363.12.7.175.2.1185401640.squirrel@webmail.sonic.net>
On Wed, Jul 25, 2007 at 03:14:00PM -0700, msnyder@sonic.net wrote:
> If reloc_size is zero, we could reach this point with a null pointer,
> and dereference it.
No, because reloc_count will always be zero if reloc_size is zero.
This function could do with a cleanup though.
* reloc.c (bfd_generic_get_relocated_section_contents): Avoid
bfd_canonicalize_reloc call when bfd_get_reloc_upper_bound
says there are no relocs.
Index: bfd/reloc.c
===================================================================
RCS file: /cvs/src/src/bfd/reloc.c,v
retrieving revision 1.168
diff -u -p -r1.168 reloc.c
--- bfd/reloc.c 3 Jul 2007 14:26:42 -0000 1.168
+++ bfd/reloc.c 26 Jul 2007 09:27:41 -0000
@@ -5185,26 +5185,28 @@ bfd_generic_get_relocated_section_conten
bfd_boolean relocatable,
asymbol **symbols)
{
- /* Get enough memory to hold the stuff. */
bfd *input_bfd = link_order->u.indirect.section->owner;
asection *input_section = link_order->u.indirect.section;
-
- long reloc_size = bfd_get_reloc_upper_bound (input_bfd, input_section);
- arelent **reloc_vector = NULL;
+ long reloc_size;
+ arelent **reloc_vector;
long reloc_count;
bfd_size_type sz;
+ reloc_size = bfd_get_reloc_upper_bound (input_bfd, input_section);
if (reloc_size < 0)
- goto error_return;
-
- reloc_vector = bfd_malloc (reloc_size);
- if (reloc_vector == NULL && reloc_size != 0)
- goto error_return;
+ return NULL;
/* Read in the section. */
sz = input_section->rawsize ? input_section->rawsize : input_section->size;
if (!bfd_get_section_contents (input_bfd, input_section, data, 0, sz))
- goto error_return;
+ return NULL;
+
+ if (reloc_size == 0)
+ return data;
+
+ reloc_vector = bfd_malloc (reloc_size);
+ if (reloc_vector == NULL)
+ return NULL;
reloc_count = bfd_canonicalize_reloc (input_bfd,
input_section,
@@ -5289,12 +5291,11 @@ bfd_generic_get_relocated_section_conten
}
}
}
- if (reloc_vector != NULL)
- free (reloc_vector);
+
+ free (reloc_vector);
return data;
error_return:
- if (reloc_vector != NULL)
- free (reloc_vector);
+ free (reloc_vector);
return NULL;
}
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2007-07-26 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 22:42 msnyder
2007-07-26 11:12 ` Alan Modra [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=20070726093721.GE11649@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sourceware.org \
--cc=msnyder@sonic.net \
/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).