[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGXu5j+PjtxDD7sCCPwVf8=Ofzx-=6OT14xAKdV3vGqJDgx7XA@mail.gmail.com>
Date: Wed, 5 Dec 2018 19:55:20 -0800
From: Kees Cook <keescook@...omium.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Anders Roxell <anders.roxell@...aro.org>,
Ingo Molnar <mingo@...hat.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
LKML <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH 1/3] stackleak: mark stackleak_track_stack() as notrace
On Wed, Dec 5, 2018 at 7:43 PM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Wed, 5 Dec 2018 19:29:11 -0800
> Kees Cook <keescook@...omium.org> wrote:
>
> > On Wed, Dec 5, 2018 at 6:29 PM Steven Rostedt <rostedt@...dmis.org> wrote:
> > >
> > > On Wed, 5 Dec 2018 21:26:51 -0500
> > > Steven Rostedt <rostedt@...dmis.org> wrote:
> > >
> > > > On Wed, 5 Dec 2018 17:08:34 -0800
> > > > Kees Cook <keescook@...omium.org> wrote:
> > > >
> > >
> > > > I'll Ack the Makefile
> > > > change in the tracing directory, but the rest belongs to others.
> >
> > Okay, I wasn't sure. Anders's patch was marked "1/3" so I thought it
> > was directed at you. :)
> >
> > I'll grab this one in the gcc-plugins tree.
>
> Should I just take patch 2 then? I'm thinking it's independent too.
>
> I'm collecting patches for the next merge window right now so it wont
> really be an issue if I do.
Sure! I'm not sure what Anders's intention was, but yeah. :)
--
Kees Cook
Powered by blists - more mailing lists