Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	sfr@canb.auug.org.au, mbenes@suse.cz, llvm@lists.linux.dev
Subject: Re: [PATCH] objtool: Teach get_alt_entry() about more relocation types
Date: Thu, 30 Sep 2021 10:32:07 -0700	[thread overview]
Message-ID: <YVX0lxyRxZuN1idm@archlinux-ax161> (raw)
In-Reply-To: <YVWUvknIEVNkPvnP@hirez.programming.kicks-ass.net>

On Thu, Sep 30, 2021 at 12:43:10PM +0200, Peter Zijlstra wrote:
> 
> Occasionally objtool encounters symbol (as opposed to section)
> relocations in .altinstructions. Typically they are the alternatives
> written by elf_add_alternative() as encountered on a noinstr
> validation run on vmlinux after having already ran objtool on the
> individual .o files.
> 
> Basically this is the counterpart of commit 44f6a7c0755d ("objtool:
> Fix seg fault with Clang non-section symbols"), because when these new
> assemblers (binutils now also does this) strip the section symbols,
> elf_add_reloc_to_insn() is forced to emit symbol based relocations.
> 
> As such, teach get_alt_entry() about different relocation types.
> 
> Fixes: 9bc0bb50727c ("objtool/x86: Rewrite retpoline thunk calls")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Reported-by: Borislav Petkov <bp@alien8.de>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>

This resolves the instance of the warning that I see with clang-12:

Tested-by: Nathan Chancellor <nathan@kernel.org>

> ---
>  tools/objtool/special.c |   32 +++++++++++++++++++++++++-------
>  1 file changed, 25 insertions(+), 7 deletions(-)
> 
> --- a/tools/objtool/special.c
> +++ b/tools/objtool/special.c
> @@ -58,6 +58,24 @@ void __weak arch_handle_alternative(unsi
>  {
>  }
>  
> +static bool reloc2sec_off(struct reloc *reloc, struct section **sec, unsigned long *off)
> +{
> +	switch (reloc->sym->type) {
> +	case STT_FUNC:
> +		*sec = reloc->sym->sec;
> +		*off = reloc->sym->offset + reloc->addend;
> +		return true;
> +
> +	case STT_SECTION:
> +		*sec = reloc->sym->sec;
> +		*off = reloc->addend;
> +		return true;
> +
> +	default:
> +		return false;
> +	}
> +}
> +
>  static int get_alt_entry(struct elf *elf, struct special_entry *entry,
>  			 struct section *sec, int idx,
>  			 struct special_alt *alt)
> @@ -91,15 +109,12 @@ static int get_alt_entry(struct elf *elf
>  		WARN_FUNC("can't find orig reloc", sec, offset + entry->orig);
>  		return -1;
>  	}
> -	if (orig_reloc->sym->type != STT_SECTION) {
> -		WARN_FUNC("don't know how to handle non-section reloc symbol %s",
> +	if (!reloc2sec_off(orig_reloc, &alt->orig_sec, &alt->orig_off)) {
> +		WARN_FUNC("don't know how to handle reloc symbol type: %s",
>  			   sec, offset + entry->orig, orig_reloc->sym->name);
>  		return -1;
>  	}
>  
> -	alt->orig_sec = orig_reloc->sym->sec;
> -	alt->orig_off = orig_reloc->addend;
> -
>  	if (!entry->group || alt->new_len) {
>  		new_reloc = find_reloc_by_dest(elf, sec, offset + entry->new);
>  		if (!new_reloc) {
> @@ -116,8 +131,11 @@ static int get_alt_entry(struct elf *elf
>  		if (arch_is_retpoline(new_reloc->sym))
>  			return 1;
>  
> -		alt->new_sec = new_reloc->sym->sec;
> -		alt->new_off = (unsigned int)new_reloc->addend;
> +		if (!reloc2sec_off(new_reloc, &alt->new_sec, &alt->new_off)) {
> +			WARN_FUNC("don't know how to handle reloc symbol type: %s",
> +				  sec, offset + entry->new, new_reloc->sym->name);
> +			return -1;
> +		}
>  
>  		/* _ASM_EXTABLE_EX hack */
>  		if (alt->new_off >= 0x7ffffff0)
> 

           reply	other threads:[~2021-09-30 17:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <YVWUvknIEVNkPvnP@hirez.programming.kicks-ass.net>]

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=YVX0lxyRxZuN1idm@archlinux-ax161 \
    --to=nathan@kernel.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mbenes@suse.cz \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --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