From: Mark Brown <broonie@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
"Moreira, Joao" <joao.moreira@intel.com>,
"Jose E. Marchesi" <jemarch@gnu.org>,
clang-built-linux <llvm@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: plumbers talk on kCFI, BTI, & IBT?
Date: Fri, 15 Apr 2022 13:19:55 +0100 [thread overview]
Message-ID: <Ylli68QUuqpCqr9E@sirena.org.uk> (raw)
In-Reply-To: <Ylkhgeyeolh1AO1y@hirez.programming.kicks-ass.net>
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
On Fri, Apr 15, 2022 at 09:40:49AM +0200, Peter Zijlstra wrote:
> On Thu, Apr 14, 2022 at 02:28:08PM -0700, Nick Desaulniers wrote:
> > Hi Sami, Peter, Joao, and Mark,
> > Jose and I are currently in the planning process to put together a
> > Kernel+Toolchain microconference track at Linux Plumbers Conference
> > this year (Sept 12-14) in Dublin, Ireland. Would you all be
> > interested in a session on Control Flow Integrity in the kernel?
> > Mitigations in hardware, software, or both might be of interest to
> > discuss more in person?
>
> Yeah, I think a session on CFI in general would be good to have.
Yup, seems like a good idea.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-04-15 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 21:28 Nick Desaulniers
2022-04-15 7:40 ` Peter Zijlstra
2022-04-15 12:19 ` Mark Brown [this message]
2022-04-15 17:55 ` Moreira, Joao
2022-04-20 23:29 ` Moreira, Joao
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=Ylli68QUuqpCqr9E@sirena.org.uk \
--to=broonie@kernel.org \
--cc=jemarch@gnu.org \
--cc=joao.moreira@intel.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.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
all inboxes | Powered by JetHome®