[Bug dynamic-link/20419] files with large allocated notes crash in open_verify

cvs-commit at gcc dot gnu.org sourceware-bugzilla@sourceware.org
Fri Mar 1 17:54:00 GMT 2019


https://sourceware.org/bugzilla/show_bug.cgi?id=20419

--- Comment #9 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  c259196b5005812aa3294dbf4eeca29b266a4522 (commit)
      from  928b305d3f6773b6a8cd1202da4f7d5d9a654456 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c259196b5005812aa3294dbf4eeca29b266a4522

commit c259196b5005812aa3294dbf4eeca29b266a4522
Author: Florian Weimer <fweimer@redhat.com>
Date:   Fri Mar 1 18:53:03 2019 +0100

    elf/tst-big-note: Improve accuracy of test [BZ #20419]

    It is possible that the link editor injects an allocated ABI tag note
    before the artificial, allocated large note in the test.  Note parsing
    in open_verify stops when the first ABI tag note is encountered, so if
    the ABI tag note comes first, the problematic code is not actually
    exercised.

    Also tweak the artificial note so that it is a syntactically valid
    4-byte aligned note, in case the link editor tries to parse notes and
    process them.

    Improves the testing part of commit 0065aaaaae51cd60210ec3a7e13.

    Reviewed-by: Carlos O'Donell <carlos@redhat.com>

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog              |    8 ++++++++
 elf/Makefile           |    9 +++++++--
 elf/tst-big-note-lib.S |   10 ++++++++--
 3 files changed, 23 insertions(+), 4 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Glibc-bugs mailing list