From: Will Deacon <will@kernel.org>
To: Iurii Zaikin <yzaikin@google.com>,
PaX Team <pageexec@freemail.hu>,
Mathias Krause <minipli@googlemail.com>,
x86@kernel.org, Sven Schnelle <svens@stackframe.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Florian Weimer <fweimer@redhat.com>,
Luis Chamberlain <mcgrof@kernel.org>,
linux-kernel@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Emese Revfy <re.emese@gmail.com>,
kernel-hardening@lists.openwall.com,
Laura Abbott <labbott@redhat.com>,
Brad Spengler <spender@grsecurity.net>,
Thomas Gleixner <tglx@linutronix.de>,
Jessica Yu <jeyu@kernel.org>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Kees Cook <keescook@chromium.org>,
linux-kbuild@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Peter Collingbourne <pcc@google.com>,
Naohiro Aota <naohiro.aota@wdc.com>,
Alexander Monakov <amonakov@ispras.ru>,
Thiago Jung Bauermann <bauerman@linux.ibm.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Alexander Popov <alex.popov@linux.com>,
gcc@gcc.gnu.org, Jann Horn <jannh@google.com>,
linux-arm-kernel@lists.infradead.org
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
notify@kernel.org
Subject: Re: [PATCH v2 0/5] Improvements of the stackleak gcc plugin
Date: Wed, 24 Jun 2020 14:54:49 +0100 [thread overview]
Message-ID: <159300400829.52405.11593787740425104484.b4-ty@kernel.org> (raw)
In-Reply-To: <20200624123330.83226-1-alex.popov@linux.com>
On Wed, 24 Jun 2020 15:33:25 +0300, Alexander Popov wrote:
> This is the v2 of the patch series with various improvements of the
> stackleak gcc plugin.
>
> The first three patches disable unneeded gcc plugin instrumentation for
> some files.
>
> The fourth patch is the main improvement. It eliminates an unwanted
> side-effect of kernel code instrumentation performed by stackleak gcc
> plugin. This patch is a deep reengineering of the idea described on
> grsecurity blog:
> https://grsecurity.net/resolving_an_unfortunate_stackleak_interaction
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: vdso: Don't use gcc plugins for building vgettimeofday.c
https://git.kernel.org/arm64/c/e56404e8e475
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Iurii Zaikin <yzaikin@google.com>,
PaX Team <pageexec@freemail.hu>,
Mathias Krause <minipli@googlemail.com>,
x86@kernel.org, Sven Schnelle <svens@stackframe.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Florian Weimer <fweimer@redhat.com>,
Luis Chamberlain <mcgrof@kernel.org>,
linux-kernel@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Emese Revfy <re.emese@gmail.com>,
kernel-hardening@lists.openwall.com,
Laura Abbott <labbott@redhat.com>,
Brad Spengler <spender@grsecurity.net>,
Thomas Gleixner <tglx@linutronix.de>,
Jessica Yu <jeyu@kernel.org>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Kees Cook <keescook@chromium.org>,
linux-kbuild@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Peter Collingbourne <pcc@google.com>,
Naohiro Aota <naohiro.aota@wdc.com>,
Alexander Monakov <amonakov@ispras.ru>,
Thiago Jung Bauermann <bauerman@linux.ibm.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Alexander Popov <alex.popov@linux.com>,
gcc@gcc.gnu.org, Jann Horn <jannh@google.com>,
linux-arm-kernel@lists.infradead.org
Cc: Will Deacon <will@kernel.org>,
kernel-team@android.com, notify@kernel.org
Subject: Re: [PATCH v2 0/5] Improvements of the stackleak gcc plugin
Date: Wed, 24 Jun 2020 14:54:49 +0100 [thread overview]
Message-ID: <159300400829.52405.11593787740425104484.b4-ty@kernel.org> (raw)
In-Reply-To: <20200624123330.83226-1-alex.popov@linux.com>
On Wed, 24 Jun 2020 15:33:25 +0300, Alexander Popov wrote:
> This is the v2 of the patch series with various improvements of the
> stackleak gcc plugin.
>
> The first three patches disable unneeded gcc plugin instrumentation for
> some files.
>
> The fourth patch is the main improvement. It eliminates an unwanted
> side-effect of kernel code instrumentation performed by stackleak gcc
> plugin. This patch is a deep reengineering of the idea described on
> grsecurity blog:
> https://grsecurity.net/resolving_an_unfortunate_stackleak_interaction
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: vdso: Don't use gcc plugins for building vgettimeofday.c
https://git.kernel.org/arm64/c/e56404e8e475
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-06-24 13:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 12:33 [PATCH v2 0/5] Improvements of the stackleak gcc plugin Alexander Popov
2020-06-24 12:33 ` Alexander Popov
2020-06-24 12:33 ` [PATCH v2 1/5] gcc-plugins/stackleak: Don't instrument itself Alexander Popov
2020-06-24 12:33 ` Alexander Popov
2020-06-24 14:52 ` Kees Cook
2020-06-24 14:52 ` Kees Cook
2020-06-24 12:33 ` [PATCH v2 2/5] ARM: vdso: Don't use gcc plugins for building vgettimeofday.c Alexander Popov
2020-06-24 12:33 ` Alexander Popov
2020-06-24 12:52 ` Luis Chamberlain
2020-06-24 12:52 ` Luis Chamberlain
2020-06-24 12:56 ` Alexander Popov
2020-06-24 12:56 ` Alexander Popov
2020-06-24 14:52 ` Kees Cook
2020-06-24 14:52 ` Kees Cook
2020-06-24 12:33 ` [PATCH v2 3/5] arm64: " Alexander Popov
2020-06-24 12:33 ` Alexander Popov
2020-06-24 12:41 ` Will Deacon
2020-06-24 12:41 ` Will Deacon
2020-06-24 14:46 ` Kees Cook
2020-06-24 14:46 ` Kees Cook
2020-06-24 12:33 ` [PATCH v2 4/5] gcc-plugins/stackleak: Use asm instrumentation to avoid useless register saving Alexander Popov
2020-06-24 12:33 ` Alexander Popov
2020-06-24 12:33 ` [PATCH v2 5/5] gcc-plugins/stackleak: Add 'verbose' plugin parameter Alexander Popov
2020-06-24 12:33 ` Alexander Popov
2020-06-24 12:53 ` Luis Chamberlain
2020-06-24 12:53 ` Luis Chamberlain
2020-06-24 13:09 ` Alexander Popov
2020-06-24 13:09 ` Alexander Popov
2020-06-24 14:41 ` Kees Cook
2020-06-24 14:41 ` Kees Cook
2020-06-24 14:53 ` Kees Cook
2020-06-24 14:53 ` Kees Cook
2020-06-24 13:54 ` Will Deacon [this message]
2020-06-24 13:54 ` [PATCH v2 0/5] Improvements of the stackleak gcc plugin Will Deacon
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=159300400829.52405.11593787740425104484.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.popov@linux.com \
--cc=amonakov@ispras.ru \
--cc=bauerman@linux.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jannh@google.com \
--cc=jeyu@kernel.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kernel-team@android.com \
--cc=labbott@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=minipli@googlemail.com \
--cc=naohiro.aota@wdc.com \
--cc=notify@kernel.org \
--cc=pageexec@freemail.hu \
--cc=pcc@google.com \
--cc=re.emese@gmail.com \
--cc=spender@grsecurity.net \
--cc=svens@stackframe.org \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
--cc=yzaikin@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 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.