public inbox for gnu-gabi@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Carlos O'Donell <carlos@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
	 Generic System V Application Binary Interface
	<generic-abi@googlegroups.com>,
	 gnu-gabi@sourceware.org
Subject: Re: RFC: Audit external function called indirectly via GOT
Date: Mon, 01 Jan 2018 00:00:00 -0000	[thread overview]
Message-ID: <87po3wo589.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <3a203b82-1247-5538-4848-92c9227cc77e@redhat.com> (Carlos	O'Donell's message of "Wed, 21 Mar 2018 15:54:22 -0600")

* Carlos O'Donell:

> On 03/21/2018 03:04 PM, Florian Weimer wrote:
>> * H. J. Lu:
>> 
>>>> Could we ship a template for the PLT entries in ld.so instead?  And if
>>>> needed, map it from the file together with an address array, like this?
>>>
>>> This won't work since linker needs to know exactly PLT layout to generate
>>> JUMP_SLOT relocations for LD_AUDIT.
>> 
>> Why would we need JUMP_SLOT relocations?  Couldn't we install suitable
>> interceptors for GLOB_DAT relocations instead, as long as they resolve
>> to external function symbols?
>
> I think your suggestion might work, but why alter the existing
> behaviour which users expect and is documented in countless linker
> text books?

If you have references, please add them to the glibc implementation or
the wiki.  It would certainly help those who are trying to work on the
code.

My understanding is that the whole thing is quite underdocumented.
For LD_AUDIT in particular, we only have the Solaris documentation,
and that's for an independent implementation.

> Existing tooling to process such relocations and entries could
> remain unchanged and we would continue to support LD_AUDIT.

My understanding is that H.J.'s proposal requires changes when running
in non-audit mode.  It certainly requires relinking all binaries,
perhaps even with special flags.

Using ld.so-generated thunks for all GLOB_DAT function symbol
relocations would happen in audit mode only and should work with
existing binaries which were built with -Wl,-z,now.

  reply	other threads:[~2018-03-22  9:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01  0:00 H.J. Lu
2018-01-01  0:00 ` Florian Weimer
2018-01-01  0:00   ` H.J. Lu
2018-01-01  0:00     ` Florian Weimer
2018-01-01  0:00       ` H.J. Lu
2018-01-01  0:00         ` Florian Weimer
2018-01-01  0:00     ` Florian Weimer
2018-01-01  0:00       ` Carlos O'Donell
2018-01-01  0:00         ` Florian Weimer [this message]
2018-01-01  0:00           ` Carlos O'Donell
2018-01-01  0:00             ` Florian Weimer
2018-01-01  0:00               ` H.J. Lu
2018-01-01  0:00                 ` Florian Weimer
2018-01-01  0:00                   ` H.J. Lu
2018-01-01  0:00             ` H.J. Lu
2018-01-01  0:00               ` Carlos O'Donell
2018-01-01  0:00             ` Cary Coutant
2018-01-01  0:00               ` H.J. Lu
2018-01-01  0:00                 ` Cary Coutant
2018-01-01  0:00                   ` H.J. Lu
2018-01-01  0:00                     ` Cary Coutant
2018-01-01  0:00           ` H.J. Lu
2018-01-01  0:00 ` Cary Coutant
2018-01-01  0:00   ` Carlos O'Donell
2018-01-01  0:00     ` Cary Coutant
2018-01-01  0:00       ` Alan Modra
2018-01-01  0:00         ` H.J. Lu
2018-01-01  0:00           ` Alan Modra
2018-01-01  0:00             ` H.J. Lu
2018-01-01  0:00       ` H.J. Lu
2018-01-01  0:00         ` Cary Coutant
2018-01-01  0:00           ` H.J. Lu
2018-01-01  0:00           ` Cary Coutant

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=87po3wo589.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=carlos@redhat.com \
    --cc=generic-abi@googlegroups.com \
    --cc=gnu-gabi@sourceware.org \
    --cc=hjl.tools@gmail.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).