From: Joao Moreira <joao@overdrivepizza.com>
To: Kees Cook <keescook@chromium.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, hjl.tools@gmail.com, jpoimboe@redhat.com,
andrew.cooper3@citrix.com, linux-kernel@vger.kernel.org,
ndesaulniers@google.com, samitolvanen@google.com,
llvm@lists.linux.dev
Subject: Re: [RFC][PATCH 6/6] objtool: Add IBT validation / fixups
Date: Tue, 08 Feb 2022 21:18:44 -0800 [thread overview]
Message-ID: <9ea50c51ee8db366430c9dc697a83923@overdrivepizza.com> (raw)
In-Reply-To: <202202082003.FA77867@keescook>
> Ah, excellent, thanks for the pointers. There's also this in the works:
> https://reviews.llvm.org/D119296 (a new CFI mode, designed to play nice
> to objtool, IBT, etc.)
Oh, great! Thanks for pointing it out. I guess I saw something with a
similar name before ;)
https://www.blackhat.com/docs/asia-17/materials/asia-17-Moreira-Drop-The-Rop-Fine-Grained-Control-Flow-Integrity-For-The-Linux-Kernel.pdf
Jokes aside (and perhaps questions more targeted to Sami), from a
diagonal look it seems that this follows the good old tag approach
proposed by PaX/grsecurity, right? If this is the case, should I assume
it could also benefit from features like -mibt-seal? Also are you
considering that perhaps we can use alternatives to flip different CFI
instrumentation as suggested by PeterZ in another thread?
Tks,
Joao
next prev parent reply other threads:[~2022-02-09 5:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211122170301.764232470@infradead.org>
[not found] ` <20211122170805.338489412@infradead.org>
[not found] ` <6ebb0ab131c522f20c094294d49091fc@overdrivepizza.com>
[not found] ` <202202081541.900F9E1B@keescook>
[not found] ` <ad6c2633f39e39583bc5c5eaf7ccbe52@overdrivepizza.com>
2022-02-09 4:05 ` [RFC][PATCH 6/6] objtool: Add IBT validation / fixups Kees Cook
2022-02-09 5:18 ` Joao Moreira [this message]
2022-02-11 13:38 ` Peter Zijlstra
2022-02-14 21:38 ` Sami Tolvanen
2022-02-14 22:25 ` Peter Zijlstra
2022-02-15 16:56 ` Sami Tolvanen
2022-02-15 20:03 ` Kees Cook
2022-02-15 21:05 ` Peter Zijlstra
2022-02-15 23:05 ` Kees Cook
2022-02-15 23:38 ` Joao Moreira
2022-02-16 12:24 ` Peter Zijlstra
2022-02-15 20:53 ` Peter Zijlstra
2022-02-15 22:45 ` Joao Moreira
2022-02-16 0:57 ` Andrew Cooper
2022-03-02 3:06 ` Peter Collingbourne
2022-03-02 3:32 ` Joao Moreira
2022-06-08 17:53 ` Fāng-ruì Sòng
2022-06-09 0:05 ` Sami Tolvanen
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=9ea50c51ee8db366430c9dc697a83923@overdrivepizza.com \
--to=joao@overdrivepizza.com \
--cc=andrew.cooper3@citrix.com \
--cc=hjl.tools@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=x86@kernel.org \
/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