public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
* [PATCH] Fix potential wrong-code issue in write_dso
@ 2019-01-01  0:00 Tom de Vries
  2019-01-01  0:00 ` [committed] Make updating sections after section header string table order-independent Tom de Vries
  0 siblings, 1 reply; 2+ messages in thread
From: Tom de Vries @ 2019-01-01  0:00 UTC (permalink / raw)
  To: dwz, jakub

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;

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-06-25 14:41 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-01  0:00 [PATCH] Fix potential wrong-code issue in write_dso Tom de Vries
2019-01-01  0:00 ` [committed] Make updating sections after section header string table order-independent Tom de Vries

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).