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: Fri, 15 Apr 2022 10:33:58 -0700 [thread overview]
Message-ID: <202204151024.DFDBF9DD6@keescook> (raw)
In-Reply-To: <CAKwvOd=CqOfd=zprWQPYoddgnGPJMb_sdk2Eut9DZNJq_fFJ-w@mail.gmail.com>
On Fri, Apr 15, 2022 at 10:17:46AM -0700, Nick Desaulniers wrote:
> On Fri, Apr 15, 2022 at 7:50 AM Qing Zhao <qing.zhao@oracle.com> wrote:
> >
> > Hi, Nick,
> >
> > > On Apr 14, 2022, at 4:30 PM, Nick Desaulniers <ndesaulniers@google.com> 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? Do you plan to attend
> > > plumbers this year which will be in person?
> >
> > I’d love to attend plumbers this year to meet people in person!
> > But not sure whether there will be enough new, big stuff to report this year since mostly bunch of bug fixes and minor
> > Improvements to the previous work.
>
> No worries; it doesn't need to be a presentation, or just one person
> presenting. I think a quick review of newly developed features from
> various authors, then a discussion with consumers (kernel developers)
> would be beneficial.
Yeah, this kind of overview is what I've been doing the last few years
(with Qing last year):
https://outflux.net/slides/2021/lpc/compiler-security-features.pdf
https://outflux.net/slides/2020/lpc/gcc-and-clang-security-feature-parity.pdf
https://outflux.net/slides/2019/lpc/gcc-and-clang.pdf
--
Kees Cook
next prev parent reply other threads:[~2022-04-15 17:34 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
2022-04-15 14:50 ` Qing Zhao
2022-04-15 17:17 ` Nick Desaulniers
2022-04-15 17:33 ` Kees Cook [this message]
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=202204151024.DFDBF9DD6@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.