Hi Will, On Mon, Jul 2, 2018 at 2:59 AM, Will Deacon <will.dea...@arm.com> wrote: > On Fri, Jun 29, 2018 at 01:25:20PM -0700, Kees Cook wrote: >> No worries! I've made the change locally and will push this out to >> -next unless there are objections? > > I'm a bit wary of conflicts in entry.S, since it's likely that we're going > to have a lot going on in there for 4.19. > > Could I take this via arm64 instead, please, or are there dependencies > on other parts of your tree?
It depends on the plugin existing, but we could split it up so the arm64 part could go separately. It would just be a no-op in the arm64 tree since CONFIG_GCC_PLUGIN_STACKLEAK won't exist there. Whatever works best for you! -Kees -- Kees Cook Pixel Security
