From: Kees Cook <keescook@chromium.org>
To: Matt Helsley <mhelsley@vmware.com>,
Sami Tolvanen <samitolvanen@google.com>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
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 11:03:18 -0700 [thread overview]
Message-ID: <202006161101.34B26E6@keescook> (raw)
In-Reply-To: <20200424222214.GC9040@rlwimi.vmware.com>
On Fri, Apr 24, 2020 at 03:22:14PM -0700, Matt Helsley wrote:
> On Fri, Apr 24, 2020 at 12:30:46PM -0700, Sami Tolvanen wrote:
> > When compiling a kernel with Clang and LTO, we need to run
> > recordmcount on vmlinux.o with a large number of sections, which
> > currently fails as the program doesn't understand extended
> > section indexes. This change adds support for processing binaries
> > with >64k sections.
> >
> > Signed-off-by: Sami Tolvanen <samitolvanen@google.com>
>
> Feel free to add
>
> 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/
>
> > ---
> > Changes in v2:
> > - Switched to unsigned int for (old|new)_shnum in append_func.
> > - Added set_shnum and find_symtab helper functions and moved
> > the new logic there.
> >
> > ---
> > scripts/recordmcount.h | 98 +++++++++++++++++++++++++++++++++++++++---
> > 1 file changed, 92 insertions(+), 6 deletions(-)
>
> <snip>
--
Kees Cook
next prev parent reply other threads:[~2020-06-16 18:03 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 [this message]
2020-06-16 18:38 ` Steven Rostedt
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=202006161101.34B26E6@keescook \
--to=keescook@chromium.org \
--cc=gregkh@linuxfoundation.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=rostedt@goodmis.org \
--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