From: Kees Cook <keescook@chromium.org>
To: Russell King <linux@armlinux.org.uk>
Cc: kbuild test robot <lkp@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Emese Revfy <re.emese@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
Laura Abbott <labbott@redhat.com>,
Kernel Hardening <kernel-hardening@lists.openwall.com>
Subject: Re: [PATCH v3] ARM: smp: add support for per-task stack canaries
Date: Wed, 12 Dec 2018 13:26:26 -0800 [thread overview]
Message-ID: <CAGXu5j+FzZ7FuhLvfR6Lm_d7dN2Pc3qn7xaqV6HLp6xtGy+kGg@mail.gmail.com> (raw)
In-Reply-To: <CAGXu5j+WLpjNq0p41eu+VeZxV3yeTB19uNYxCQevbcDYkv7gJw@mail.gmail.com>
On Mon, Dec 10, 2018 at 2:34 PM Kees Cook <keescook@chromium.org> wrote:
>
> On Sun, Dec 9, 2018 at 2:38 AM Russell King - ARM Linux
> <linux@armlinux.org.uk> wrote:
> >
> > On Sun, Dec 09, 2018 at 06:28:11PM +0800, kbuild test robot wrote:
> > > Hi Ard,
> > >
> > > I love your patch! Perhaps something to improve:
> >
> > Hi,
> >
> > This looks to me like a false warning - how can a patch touching arch
> > code affect the result of lib/test_ubsan.c? Please can you double-
> > check this result?
>
> Yeah, no idea. Do you want me to toss this into the ARM patch queue?
> If not, I can this through the gcc-plugin tree.
Since the ARM changes are relatively small, and it adds a new plugin,
I'll take this via the gcc-plugins tree for -next now. Please yell if
this should be done differently.
Thanks!
--
Kees Cook
next prev parent reply other threads:[~2018-12-12 21:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 8:32 [PATCH v3] ARM: smp: add support for per-task stack canaries Ard Biesheuvel
2018-12-09 10:28 ` kbuild test robot
2018-12-09 10:37 ` Russell King - ARM Linux
2018-12-10 22:34 ` Kees Cook
2018-12-12 21:26 ` Kees Cook [this message]
2018-12-13 2:53 ` [kbuild-all] " Rong Chen
2019-01-09 6:30 ` Rong Chen
2019-01-09 21:37 ` Kees Cook
2020-03-09 16:49 ` Guenter Roeck
2020-03-11 17:21 ` Kees Cook
2020-03-11 18:31 ` Guenter Roeck
2020-03-11 18:47 ` Kees Cook
2020-03-11 20:45 ` Russell King - ARM Linux admin
2020-03-11 21:39 ` Guenter Roeck
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=CAGXu5j+FzZ7FuhLvfR6Lm_d7dN2Pc3qn7xaqV6HLp6xtGy+kGg@mail.gmail.com \
--to=keescook@chromium.org \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=kbuild-all@01.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=re.emese@gmail.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;
as well as URLs for NNTP newsgroup(s).