[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180727205511.7c0f2e62@canb.auug.org.au>
Date: Fri, 27 Jul 2018 20:55:11 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Kees Cook <keescook@...gle.com>
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Alexander Popov <alex.popov@...ux.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Laura Abbott <labbott@...hat.com>
Subject: Re: linux-next: build failure after merge of the kspp tree
Hi all,
On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > After merging the kspp tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > cc1: error: plugin stackleak_plugin should be specified before -fplugin-arg-stackleak_plugin-disable in the command line
> >
> > Maybe caused by commit
> >
> > a8b9eaddb9c0 ("gcc-plugins: Add STACKLEAK plugin for tracking the kernel stack")
> >
> > I have used the kspp tree from next-20180726 for today.
>
> Well, that obviously didn't work since the tree hasn't changed for a
> few days.
>
> I can't see what has interacted to make this happen, so I have dropped
> the kspp tree for today.
Actually, it may have been caused by commit
0b3e336601b8 ("arm64: Add support for STACKLEAK gcc plugin")
from the arm64 tree.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists