From: Joao Moreira <joao@overdrivepizza.com>
To: Rui Ueyama <rui314@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
"Moreira, Joao" <joao.moreira@intel.com>,
Andi Kleen <andi@firstfloor.org>,
x86-64-abi <x86-64-abi@googlegroups.com>,
Binutils <binutils@sourceware.org>,
i@maskray.me
Subject: Re: x86-64: new CET-enabled PLT format proposal
Date: Tue, 01 Mar 2022 01:45:20 -0800 [thread overview]
Message-ID: <a23a08c923608f41ad396b2763e13080@overdrivepizza.com> (raw)
In-Reply-To: <CACKH++YTZVk3Vo_u1SvrGKed1Eq3h4WW-Oj6dPQ0kr+Lp89f8w@mail.gmail.com>
On 2022-03-01 01:32, Rui Ueyama wrote:
> On Tue, Mar 1, 2022 at 6:27 PM Joao Moreira <joao@overdrivepizza.com>
> wrote:
>>
>> > This is what I tried first but I then realized that I needed to insert
>> > another `endbr` between `jmp` and `call`. `jmp GOT[foo]` can jump only
>> > to `endbr` if CET is enabled, so it can't directly jump to the
>> > following `call`.
>> >
>> Ugh, there we go... dead. Thanks for not letting me waste a ton of
>> time
>> :)
>
> I actually wasted my time by implementing it only to find that it
> wouldn't work. :) If you are interested, this is my commit to my
> linker.
> https://github.com/rui314/mold/commit/4ec0bbf04841e514aca2000f3d780d14efcaefc9
I'm glad I posted it here before trying to go and implement :)
Regarding the projects mentioned by HJ, I assume one of them is this (in
case you are curious):
https://static.sched.com/hosted_files/lssna2021/8f/LSS_FINEIBT_JOAOMOREIRA.pdf
In FineIBT we use R11 to pass hashes around through direct calls to
enable fine-grain CFI on top of IBT.
next prev parent reply other threads:[~2022-03-01 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 3:18 Rui Ueyama
2022-02-27 15:06 ` H.J. Lu
2022-02-28 3:46 ` Rui Ueyama
2022-03-01 0:04 ` H.J. Lu
2022-03-01 0:30 ` Rui Ueyama
2022-03-01 2:22 ` Fangrui Song
2022-03-01 9:16 ` Joao Moreira
2022-03-01 9:25 ` Rui Ueyama
2022-03-01 9:27 ` Joao Moreira
2022-03-01 9:32 ` Rui Ueyama
2022-03-01 9:45 ` Joao Moreira [this message]
2022-03-01 9:48 ` Rui Ueyama
2022-03-01 10:35 ` Florian Weimer
2022-03-01 22:16 ` Fangrui Song
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=a23a08c923608f41ad396b2763e13080@overdrivepizza.com \
--to=joao@overdrivepizza.com \
--cc=andi@firstfloor.org \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=i@maskray.me \
--cc=joao.moreira@intel.com \
--cc=rui314@gmail.com \
--cc=x86-64-abi@googlegroups.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).