public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>, x86 <x86@kernel.org>,
	linux-tip-commits@vger.kernel.org,
	Sami Tolvanen <samitolvanen@google.com>,
	Kristen Carlson Accardi <kristen@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [tip: objtool/core] objtool: Use sh_info to find the base for .rela sections
Date: Tue, 16 Jun 2020 17:11:28 -0700	[thread overview]
Message-ID: <202006161708.8CC6F4974@keescook> (raw)
In-Reply-To: <20200616192749.GB2531@hirez.programming.kicks-ass.net>

On Tue, Jun 16, 2020 at 09:27:49PM +0200, Peter Zijlstra wrote:
> On Tue, Jun 16, 2020 at 11:00:59AM -0700, Kees Cook wrote:
> > On Wed, Apr 22, 2020 at 10:24:44PM -0000, tip-bot2 for Sami Tolvanen wrote:
> > > The following commit has been merged into the objtool/core branch of tip:
> > > 
> > > Commit-ID:     e2ccbff8f02d6b140b8ee71108264686c19b1c78
> > > Gitweb:        https://git.kernel.org/tip/e2ccbff8f02d6b140b8ee71108264686c19b1c78
> > > Author:        Sami Tolvanen <samitolvanen@google.com>
> > > AuthorDate:    Tue, 21 Apr 2020 11:25:01 -07:00
> > > Committer:     Josh Poimboeuf <jpoimboe@redhat.com>
> > > CommitterDate: Tue, 21 Apr 2020 18:49:15 -05:00
> > > 
> > > objtool: Use sh_info to find the base for .rela sections
> > > 
> > > ELF doesn't require .rela section names to match the base section. Use
> > > the section index in sh_info to find the section instead of looking it
> > > up by name.
> > > 
> > > LLD, for example, generates a .rela section that doesn't match the base
> > > section name when we merge sections in a linker script for a binary
> > > compiled with -ffunction-sections.
> > > 
> > > Signed-off-by: Sami Tolvanen <samitolvanen@google.com>
> > > Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
> > > Reviewed-by: Kees Cook <keescook@chromium.org>
> > 
> > Hi!
> > 
> > Where did this commit end up? It seems to have vanished (404 on the
> > Gitweb link) and isn't in -next nor Linus's tree.
> > 
> > This is needed for LTO, FGKASLR, and link speed improvements[1]. Is it
> > possible to get this landed in -rc2 so all the things depending on it
> > can rebase happily?
> 
> I can't remember why this happened, however I think this patch is in
> josh's objtool tree that I was going to stick in objtool/core
> tomorrow-ish.

Okay, thanks!

> Are those things you mentioned still slated for this release?

No, the three things I mentioned aren't for v5.8 (they're still under
development), but sending their respective series without the -tip
patches in -rc2 will result in redundant patches. (So, it's hardly the
end of the world, but it's just a confusing state to be in since they
appeared in -tip and then never ended up in the merge window. It'd be
helpful to have them in place for things that will base their latest
tree on v5.8-rc2.)

-- 
Kees Cook

  reply	other threads:[~2020-06-17  0:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 22:24 [tip: objtool/core] objtool: Use sh_info to find the base for .rela sections tip-bot2 for Sami Tolvanen
2020-06-16 18:00 ` Kees Cook
2020-06-16 19:27   ` Peter Zijlstra
2020-06-17  0:11     ` Kees Cook [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-17 10:04 tip-bot2 for Sami Tolvanen

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=202006161708.8CC6F4974@keescook \
    --to=keescook@chromium.org \
    --cc=jpoimboe@redhat.com \
    --cc=kristen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=samitolvanen@google.com \
    --cc=x86@kernel.org \
    /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