From: Steven Rostedt <rostedt@goodmis.org>
To: Kees Cook <keescook@chromium.org>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/3] stackleak: mark stackleak_track_stack() as notrace
Date: Wed, 5 Dec 2018 22:43:33 -0500 [thread overview]
Message-ID: <20181205224333.3c589916@vmware.local.home> (raw)
In-Reply-To: <CAGXu5jJeyBRHPhKKRyp1=NCCdBfrJw=mdg4+XCEL413ZtkyU1A@mail.gmail.com>
On Wed, 5 Dec 2018 19:29:11 -0800
Kees Cook <keescook@chromium.org> wrote:
> On Wed, Dec 5, 2018 at 6:29 PM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > On Wed, 5 Dec 2018 21:26:51 -0500
> > Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > > On Wed, 5 Dec 2018 17:08:34 -0800
> > > Kees Cook <keescook@chromium.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.
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Kees Cook <keescook@chromium.org>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] stackleak: mark stackleak_track_stack() as notrace
Date: Wed, 5 Dec 2018 22:43:33 -0500 [thread overview]
Message-ID: <20181205224333.3c589916@vmware.local.home> (raw)
In-Reply-To: <CAGXu5jJeyBRHPhKKRyp1=NCCdBfrJw=mdg4+XCEL413ZtkyU1A@mail.gmail.com>
On Wed, 5 Dec 2018 19:29:11 -0800
Kees Cook <keescook@chromium.org> wrote:
> On Wed, Dec 5, 2018 at 6:29 PM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > On Wed, 5 Dec 2018 21:26:51 -0500
> > Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > > On Wed, 5 Dec 2018 17:08:34 -0800
> > > Kees Cook <keescook@chromium.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.
-- Steve
_______________________________________________
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:[~2018-12-06 3:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 15:08 [PATCH 1/3] stackleak: mark stackleak_track_stack() as notrace Anders Roxell
2018-11-30 15:08 ` Anders Roxell
2018-11-30 15:21 ` Steven Rostedt
2018-11-30 15:21 ` Steven Rostedt
2018-12-06 1:08 ` Kees Cook
2018-12-06 1:08 ` Kees Cook
2018-12-06 2:26 ` Steven Rostedt
2018-12-06 2:26 ` Steven Rostedt
2018-12-06 2:29 ` Steven Rostedt
2018-12-06 2:29 ` Steven Rostedt
2018-12-06 3:29 ` Kees Cook
2018-12-06 3:29 ` Kees Cook
2018-12-06 3:43 ` Steven Rostedt [this message]
2018-12-06 3:43 ` Steven Rostedt
2018-12-06 3:55 ` Kees Cook
2018-12-06 3:55 ` Kees Cook
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=20181205224333.3c589916@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=will.deacon@arm.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.