From: Carlos O'Donell <carlos@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Florian Weimer <fw@deneb.enyo.de>,
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: <b7c49ff0-4a46-77ca-44f5-0b268e08aca1@redhat.com> (raw)
In-Reply-To: <CAMe9rOogarcRF1OzM3NbTGUH_7+JH9oduMWu8mdHjwy_-qsY0Q@mail.gmail.com>
On 03/22/2018 11:01 AM, H.J. Lu wrote:
> On Thu, Mar 22, 2018 at 8:36 AM, Carlos O'Donell <carlos@redhat.com> wrote:
>>> 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.
>>
>> This is a very good reason to prefer one method over another, that we
>> could fix existing binaries. However, I still think the complexity of
>> such a fix outweighs what we are trying to fix. Do we have another use
>> for such stubs?
>
> If you take a look at BFD linker, it generates different PLT layouts for
> MPX and CET. It is totally transparent to ld.so. Putting all PLT choices
> as well as adding new ones in ld.so is very complex. I don't believe they
> belong to ld.so.
Belief is not a good reason to choose one technical solution over another.
I agree with your statements though, there would be a lot of additional
complexity added to ld.so without much apparent gain for that complexity
e.g. fixing existing -fno-plt binaries to work with LD_AUDIT. Which is why
I asked Florian if he had *other* uses for the stubs, since that might
change the balance. I admit it would have to be a very good reason to make
me consider the added complexity to balance the use case.
I think your solution as you have defined it is the best option, but we
should circle back and make sure we answer all of Cary and Alan's questions
to their satisfaction and gain consensus.
Cheers,
Carlos.
next prev parent reply other threads:[~2018-03-22 16:06 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 ` Carlos O'Donell
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Carlos O'Donell [this message]
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 ` 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 ` Florian Weimer
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Florian Weimer
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 ` Cary Coutant
2018-01-01 0:00 ` H.J. Lu
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=b7c49ff0-4a46-77ca-44f5-0b268e08aca1@redhat.com \
--to=carlos@redhat.com \
--cc=fw@deneb.enyo.de \
--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).