public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Cc: Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH] libebl: Allow SHT_NOTE as relocation target type.
Date: Thu, 22 Feb 2018 12:17:00 -0000	[thread overview]
Message-ID: <1519301841.3316.3.camel@klomp.org> (raw)
In-Reply-To: <1519227364-17006-1-git-send-email-mark@klomp.org>

On Wed, 2018-02-21 at 16:36 +0100, Mark Wielaard wrote:
> eu-elflint uses ebl_check_reloc_target_type to determine whether a section
> is a valid relocation target. In Fedora rawhide there are new ELF notes
> (annobin) which have relocations against them in ET_REL files. eu-elflint
> currently flags these as invalid. It looks like that is not correct.
> I cannot find any reason an SHT_NOTE section cannot have relocations
> against it. So this patch allows them.

Nick agreed with me, so I pushed this to master.

      reply	other threads:[~2018-02-22 12:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 15:36 Mark Wielaard
2018-02-22 12:17 ` Mark Wielaard [this message]

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=1519301841.3316.3.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=nickc@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).