public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Qing Zhao <qing.zhao@oracle.com>,
	Bill Wendling <morbo@google.com>,
	"Moreira, Joao" <joao.moreira@intel.com>,
	clang-built-linux <llvm@lists.linux.dev>,
	LKML <linux-kernel@vger.kernel.org>,
	"Jose E. Marchesi" <jemarch@gnu.org>
Subject: Re: toolchain mitigations plumbers session
Date: Thu, 14 Apr 2022 15:51:02 -0700	[thread overview]
Message-ID: <202204141549.B1DE158@keescook> (raw)
In-Reply-To: <CAKwvOdniB-+F37ygZhRytBGVFjwnukyOpmoiJTCeusMdb=6_=g@mail.gmail.com>

On Thu, Apr 14, 2022 at 02:30:33PM -0700, Nick Desaulniers wrote:
> Hi Qing, Kees, and Bill,
> 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 leading another session on
> kernel+toolchain collaboration for mitigations?

Yes please! With work Qing and Bill (and Sami and Joao and others) have
been doing lately, this session will have a lot of new stuff to talk
about!

> Do you plan to attend
> plumbers this year which will be in person?

Yes, my current intention is to attend plumbers in person this year.
However, I reserve the right to shake the magic covid 8-ball again as
we get closer to September. :)

-Kees

-- 
Kees Cook

  parent reply	other threads:[~2022-04-14 22:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 21:30 toolchain mitigations plumbers session Nick Desaulniers
2022-04-14 21:53 ` Bill Wendling
2022-04-14 22:51 ` Kees Cook [this message]
2022-04-15 14:50 ` Qing Zhao
2022-04-15 17:17   ` Nick Desaulniers
2022-04-15 17:33     ` Kees Cook
2022-04-15 18:53     ` Qing Zhao

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=202204141549.B1DE158@keescook \
    --to=keescook@chromium.org \
    --cc=jemarch@gnu.org \
    --cc=joao.moreira@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=ndesaulniers@google.com \
    --cc=qing.zhao@oracle.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