mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Josh Poimboeuf" <jpoimboe@kernel.org>,
	"Peter Zijlstra" <peterz@infradead.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: "relocation to !ENDBR" objtool warnings
Date: Tue, 17 Dec 2024 09:54:24 +0100	[thread overview]
Message-ID: <33f3a0a3-a929-4584-af81-6e020671d428@app.fastmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3250 bytes --]

Hi Josh and Peter,

I just sent three patches for the most common objtool warnings I get
with gcc-14 on linux-next.

There is one more that I can't figure out, maybe you have an idea
already. I've attached a .config that shows the problem in two files
when built with gcc-14.2.0.

     Arnd

vmlinux.o: warning: objtool: x86_init_dev_msi_info+0x5b: relocation to !ENDBR: irq_chip_retrigger_hierarchy+0x0
vmlinux.o: warning: objtool: .export_symbol+0x3720: data relocation to !ENDBR: irq_chip_retrigger_hierarchy+0x0
vmlinux.o: warning: objtool: .export_symbol+0x252e8: data relocation to !ENDBR: stpcpy+0x0
vmlinux.o: warning: objtool: hv_pci_msi_controller+0x58: data relocation to !ENDBR: irq_chip_retrigger_hierarchy+0x0
vmlinux.o: warning: objtool: hpet_msi_controller+0x58: data relocation to !ENDBR: irq_chip_retrigger_hierarchy+0x0
vmlinux.o: warning: objtool: ioapic_ir_chip+0x58: data relocation to !ENDBR: irq_chip_retrigger_hierarchy+0x0
vmlinux.o: warning: objtool: ioapic_chip+0x58: data relocation to !ENDBR: irq_chip_retrigger_hierarchy+0x0


0000000000000210 <irq_chip_retrigger_hierarchy>:
     210:       66 66 2e 0f 1f 84 00    data16 cs nopw 0x0(%rax,%rax,1)
     217:       00 00 00 00 
     21b:       0f 1f 44 00 00          nopl   0x0(%rax,%rax,1)
     220:       f3 0f 1e fa             endbr64
     224:       48 8b 7f 28             mov    0x28(%rdi),%rdi
     228:       48 85 ff                test   %rdi,%rdi
     22b:       74 17                   je     244 <irq_chip_retrigger_hierarchy+0x34>
     22d:       48 8b 47 18             mov    0x18(%rdi),%rax
     231:       48 85 c0                test   %rax,%rax
     234:       74 ee                   je     224 <irq_chip_retrigger_hierarchy+0x14>
     236:       48 8b 40 58             mov    0x58(%rax),%rax
     23a:       48 85 c0                test   %rax,%rax
     23d:       74 e5                   je     224 <irq_chip_retrigger_hierarchy+0x14>
     23f:       e9 00 00 00 00          jmp    244 <irq_chip_retrigger_hierarchy+0x34>
                        240: R_X86_64_PLT32     __x86_indirect_thunk_rax-0x4
     244:       31 c0                   xor    %eax,%eax
     246:       31 ff                   xor    %edi,%edi
     248:       c3                      ret
     249:       0f 1f 80 00 00 00 00    nopl   0x0(%rax)

00000000000000f0 <stpcpy>:
  f0:   66 66 2e 0f 1f 84 00    data16 cs nopw 0x0(%rax,%rax,1)
  f7:   00 00 00 00 
  fb:   0f 1f 44 00 00          nopl   0x0(%rax,%rax,1)
 100:   f3 0f 1e fa             endbr64
 104:   0f b6 06                movzbl (%rsi),%eax
 107:   48 89 fa                mov    %rdi,%rdx
 10a:   48 83 c6 01             add    $0x1,%rsi
 10e:   48 83 c7 01             add    $0x1,%rdi
 112:   88 47 ff                mov    %al,-0x1(%rdi)
 115:   84 c0                   test   %al,%al
 117:   75 eb                   jne    104 <stpcpy+0x14>
 119:   48 89 d0                mov    %rdx,%rax
 11c:   31 d2                   xor    %edx,%edx
 11e:   31 f6                   xor    %esi,%esi
 120:   31 ff                   xor    %edi,%edi
 122:   c3                      ret
 123:   66 66 2e 0f 1f 84 00    data16 cs nopw 0x0(%rax,%rax,1)
 12a:   00 00 00 00 
 12e:   66 90                   xchg   %ax,%ax


[-- Attachment #2: 0x14CCB493-config.gz --]
[-- Type: application/gzip, Size: 36955 bytes --]

[-- Attachment #3: chip.o.gz --]
[-- Type: application/gzip, Size: 6509 bytes --]

[-- Attachment #4: string.o.gz --]
[-- Type: application/gzip, Size: 3445 bytes --]

             reply	other threads:[~2024-12-17  8:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17  8:54 Arnd Bergmann [this message]
2024-12-17  9:09 ` Arnd Bergmann
2024-12-17 10:37   ` Arnd Bergmann
2024-12-18  8:47   ` Josh Poimboeuf
2024-12-18 10:08     ` Peter Zijlstra
2024-12-18 10:38       ` Arnd Bergmann

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=33f3a0a3-a929-4584-af81-6e020671d428@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --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

all inboxes | Powered by JetHome®