From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] readelf: Warn zero-sized relocation sections
Date: Tue, 14 Apr 2020 06:03:59 -0700 [thread overview]
Message-ID: <CAMe9rOo8ksA3+5VcFxVgv+qeDqtf3n8+X2rGjFJp1SeFJSMKtg@mail.gmail.com> (raw)
In-Reply-To: <81ae71d0-e88e-bf62-1298-3bee538f852e@suse.com>
On Tue, Apr 14, 2020 at 5:42 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> On 14.04.2020 14:25, H.J. Lu via Binutils wrote:
> > Older linkers may fail with zero-sized relocation section in section
> > group.
> >
> > PR ld/25767
> > * readelf.c (process_section_headers): Warn zero-sized
> > relocation sections.
>
> Zero-sized sections of whatever kind are perfectly fine in ELF. I
> see no reason why one would want to see a warning for such by
> default.
Linkers older than 2.35 may fail with
./ld: BFD (GNU Binutils) 2.34.50.20200402 assertion fail
/export/gnu/import/git/gitlab/x86-binutils/bfd/elf.c:3652
> Jan
>
> > ---
> > binutils/readelf.c | 14 ++++++++++++--
> > 1 file changed, 12 insertions(+), 2 deletions(-)
> >
> > diff --git a/binutils/readelf.c b/binutils/readelf.c
> > index cd456b0290..535d47a58e 100644
> > --- a/binutils/readelf.c
> > +++ b/binutils/readelf.c
> > @@ -6315,9 +6315,19 @@ process_section_headers (Filedata * filedata)
> > else if (section->sh_type == SHT_GROUP)
> > CHECK_ENTSIZE_VALUES (section, i, GRP_ENTRY_SIZE, GRP_ENTRY_SIZE);
> > else if (section->sh_type == SHT_REL)
> > - CHECK_ENTSIZE (section, i, Rel);
> > + {
> > + CHECK_ENTSIZE (section, i, Rel);
> > + if (section->sh_size == 0)
> > + warn (_("Section '%s': zero-sized relocation section\n"),
> > + name);
> > + }
> > else if (section->sh_type == SHT_RELA)
> > - CHECK_ENTSIZE (section, i, Rela);
> > + {
> > + CHECK_ENTSIZE (section, i, Rela);
> > + if (section->sh_size == 0)
> > + warn (_("Section '%s': zero-sized relocation section\n"),
> > + name);
> > + }
> > else if ((do_debugging || do_debug_info || do_debug_abbrevs
> > || do_debug_lines || do_debug_pubnames || do_debug_pubtypes
> > || do_debug_aranges || do_debug_frames || do_debug_macinfo
> >
>
--
H.J.
next prev parent reply other threads:[~2020-04-14 13:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 12:25 H.J. Lu
2020-04-14 12:42 ` Jan Beulich
2020-04-14 13:03 ` H.J. Lu [this message]
2020-04-14 13:25 ` Jan Beulich
2020-04-14 13:30 ` H.J. Lu
2020-04-14 13:38 ` Jan Beulich
2020-04-14 13:54 ` H.J. Lu
2020-04-17 15:46 ` Nick Clifton
2020-04-17 17:57 ` H.J. Lu
2020-04-18 0:26 ` Alan Modra
2020-04-18 16:51 ` [PATCH] elf: Strip zero-sized dynamic sections H.J. Lu
2020-04-20 9:35 ` Alan Modra
2020-04-20 13:25 ` V2 " H.J. Lu
2020-04-21 10:20 ` Nick Clifton
2020-04-20 5:33 ` [PATCH] readelf: Warn zero-sized relocation sections Jan Beulich
2020-04-20 10:28 ` Nick Clifton
2020-04-20 12:19 ` Jan Beulich
2020-04-20 17:25 ` Hans-Peter Nilsson
2020-04-21 10:01 ` Nick Clifton
2020-04-21 10:31 ` Jan Beulich
2020-04-22 2:51 ` Hans-Peter Nilsson
2020-04-24 14:04 ` Nick Clifton
2020-04-24 16:20 ` Hans-Peter Nilsson
2020-04-29 15:04 ` Nick Clifton
2020-04-24 17:19 ` Fangrui Song
2020-04-26 15:26 ` Nick Clifton
2020-04-26 15:59 ` H.J. Lu
2020-04-24 17:50 ` Jan Beulich
2020-04-27 11:24 ` Nick Clifton
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=CAMe9rOo8ksA3+5VcFxVgv+qeDqtf3n8+X2rGjFJp1SeFJSMKtg@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).