From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH] elflint: Fix sh_entsize check when comparing SHT_HASH and SHT_GNU_HASH.
Date: Mon, 15 Feb 2016 23:48:45 +0100 [thread overview]
Message-ID: <20160215224845.GC29346@blokker.redhat.com> (raw)
In-Reply-To: 1455024638-12222-1-git-send-email-mjw@redhat.com
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
On Tue, Feb 09, 2016 at 02:30:38PM +0100, Mark Wielaard wrote:
> GCC6 -Wduplicated-cond found the following issue:
>
> elflint.c: In function ‘compare_hash_gnu_hash’:
> elflint.c:2483:34: error: duplicated ‘if’ condition [-Werror=duplicated-cond]
> else if (hash_shdr->sh_entsize == sizeof (Elf64_Word))
> ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
> elflint.c:2448:29: note: previously used here
> if (hash_shdr->sh_entsize == sizeof (Elf32_Word))
> ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
>
> Which is correct, a Word in both Elf32 and Elf64 files is 4 bytes.
> We meant to check for sizeof (Elf64_Xword) which is 8 bytes.
>
> Also fix the section index and name in the error message.
>
> The reason we probably didn't see this issue before is that SHT_HASH
> sections really always should have sh_entsize of 4 even on 64bit arches.
> There are however a couple of arches with mistakes in their sysv ABI.
> See libelf/common.h. This also would only be triggered if on such an
> architectures when the ELF file would have both a SHT_HASH and SHT_GNU_HASH
> section and elflint would try to compare those sections.
>
> Add an example testfile-s390x-hash-both to run-elflint-test.sh.
I pushed this to master.
next reply other threads:[~2016-02-15 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 22:48 Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-10 14:27 Jose E. Marchesi
2016-02-09 15:24 Mark Wielaard
2016-02-09 13:30 Mark Wielaard
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=20160215224845.GC29346@blokker.redhat.com \
--to=mjw@redhat.com \
--cc=elfutils-devel@lists.fedorahosted.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).