From: Linus Torvalds <torvalds@linux-foundation.org>
To: Borislav Petkov <bp@suse.de>, Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [GIT PULL] objtool/urgent for v5.15-rc4
Date: Sun, 3 Oct 2021 11:38:00 -0700 [thread overview]
Message-ID: <CAHk-=wh9JzLmwAqA2+cA=Y4x_TYNBZv_OM4eSEDFPF8V_GAPug@mail.gmail.com> (raw)
In-Reply-To: <YVl7RR5NcbPyiXgO@zn.tnic>
On Sun, Oct 3, 2021 at 2:43 AM Borislav Petkov <bp@suse.de> wrote:
>
> - Handle symbol relocations properly due to changes in the toolchains
> which remove section symbols now
Ugh.
This actually causes a new warning for me:
arch/x86/kvm/emulate.o: warning: objtool: __ex_table+0x4: don't
know how to handle reloc symbol type: kvm_fastop_exception
on an x86-64 allmodconfig build (and my normal clang build for my
actual default config too).
Looking at the kvm code, that kvm_fastop_exception thing is some funky sh*t.
I _think_ the problem is that 'kvm_fastop_exception' is done with bare
asm at the top-level and that triggers some odd interaction with other
section data, but I really don't know.
Anyway, that thing is in my public tree now, because it's better to
get it out and fixed and have the kvm people look at it.
Linus
next prev parent reply other threads:[~2021-10-03 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 9:43 [GIT PULL] objtool/urgent for v5.15-rc4 Borislav Petkov
2021-10-03 18:20 ` pr-tracker-bot
2021-10-03 18:38 ` Linus Torvalds [this message]
2021-10-03 19:02 ` Linus Torvalds
2021-10-03 19:10 ` Linus Torvalds
2021-10-03 23:02 ` Josh Poimboeuf
2021-10-04 7:28 ` Paolo Bonzini
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='CAHk-=wh9JzLmwAqA2+cA=Y4x_TYNBZv_OM4eSEDFPF8V_GAPug@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=bp@suse.de \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.