From: Steven Rostedt <rostedt@goodmis.org>
To: Kees Cook <keescook@chromium.org>
Cc: Matt Helsley <mhelsley@vmware.com>,
Sami Tolvanen <samitolvanen@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Kristen Carlson Accardi <kristen@linux.intel.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] recordmcount: support >64k sections
Date: Tue, 16 Jun 2020 14:38:44 -0400 [thread overview]
Message-ID: <20200616143844.5599804d@oasis.local.home> (raw)
In-Reply-To: <202006161101.34B26E6@keescook>
On Tue, 16 Jun 2020 11:03:18 -0700
Kees Cook <keescook@chromium.org> wrote:
> > Reviewed-by: Matt Helsley <mhelsley@vmware.com>
>
> Hi!
>
> Can this patch please be applied and sent before -rc2? FGKASLR, LTO, and
> link time improvements[1] all depend on this fix, and I'd really like
> them all to be able to sanely rebase for the development window.
>
> Thanks!
>
> -Kees
>
> [1] https://lore.kernel.org/lkml/CAK7LNARbZhoaA=Nnuw0=gBrkuKbr_4Ng_Ei57uafujZf7Xazgw@mail.gmail.com/
The patch seems to have fallen behind in my patch stack (unfortunately,
it's most recent first!)
Anyway, I'm putting together now a set of patches for -rc2. I'll
include this one in it as well.
-- Steve
next prev parent reply other threads:[~2020-06-16 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 23:24 [PATCH] recordmcount: support >64k sections Sami Tolvanen
2020-04-23 0:05 ` Steven Rostedt
2020-04-23 18:47 ` Sami Tolvanen
2020-04-23 21:47 ` Matt Helsley
2020-04-24 19:18 ` Sami Tolvanen
2020-04-24 19:30 ` [PATCH v2] " Sami Tolvanen
2020-04-24 22:22 ` Matt Helsley
2020-06-16 18:03 ` Kees Cook
2020-06-16 18:38 ` Steven Rostedt [this message]
2020-06-16 18:45 ` 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=20200616143844.5599804d@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=kristen@linux.intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhelsley@vmware.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=samitolvanen@google.com \
--cc=tglx@linutronix.de \
/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