public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [PATCH] Fix potential wrong-code issue in write_dso
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <20190315151221.GA7938@delia> (raw)

Hi,

The function write_dso has the responsibility to update:
- the file offset of the sections, and
- the file offset of the section header table.

It does this in two steps:
- it calculates the effects of adding, removing and updating
  debug sections
- it makes sure the file offsets have the required alignment

The second step may or may not update the file offsets, but if it does, it
requires the entries in the section header table to be in file offset
order.

However, if the second step does not update the file offsets, no check on
section header table order is done, which implies that the first step should
be able to handle an unsorted section header table.

That is not the case for this update loop:
...
  for (j = dso->ehdr.e_shstrndx + 1; j < dso->ehdr.e_shnum; ++j)
    dso->shdr[j].sh_offset += len;
...

This loop adds an increase of the size of the section header string table to
sections 'after' the section header string table.  But the after test here is
implemented in terms of order in the section header table, which only works if
if the section header table is sorted.

Fix this by rewriting the after test in terms of sh_offset:
...
  for (j = 1; j < dso->ehdr.e_shnum; ++j)
    if (dso->shdr[j].sh_offset
        > dso->shdr[dso->ehdr.e_shstrndx].sh_offset)
      dso->shdr[j].sh_offset += len;
...

OK for trunk?

Thanks,
- Tom

Fix potential wrong-code issue in write_dso

2019-03-15  Tom de Vries  <tdevries@suse.de>

	* dwz.c (write_dso): Make updating of sections after section header
	string table robust against unsortes section header table.

---
 dwz.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/dwz.c b/dwz.c
index 6b6a33e..5672ede 100644
--- a/dwz.c
+++ b/dwz.c
@@ -10097,8 +10097,10 @@ write_dso (DSO *dso, const char *file, struct stat *st)
 	    dso->shdr[dso->ehdr.e_shstrndx].sh_size += len;
 	    if (dso->shdr[dso->ehdr.e_shstrndx].sh_offset < min_shoff)
 	      min_shoff = dso->shdr[dso->ehdr.e_shstrndx].sh_offset;
-	    for (j = dso->ehdr.e_shstrndx + 1; j < dso->ehdr.e_shnum; ++j)
-	      dso->shdr[j].sh_offset += len;
+	    for (j = 1; j < dso->ehdr.e_shnum; ++j)
+	      if (dso->shdr[j].sh_offset
+		  > dso->shdr[dso->ehdr.e_shstrndx].sh_offset)
+		dso->shdr[j].sh_offset += len;
 	    if (ehdr.e_shoff > dso->shdr[dso->ehdr.e_shstrndx].sh_offset)
 	      ehdr.e_shoff += len;
 	    shstrtabadd += len;

             reply	other threads:[~2019-03-15 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 Tom de Vries [this message]
2019-01-01  0:00 ` [committed] Make updating sections after section header string table order-independent Tom de Vries

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=20190315151221.GA7938@delia \
    --to=tdevries@suse.de \
    --cc=dwz@sourceware.org \
    --cc=jakub@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).