From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Michael Roth <michael.roth@amd.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
bp@kernel.org, bgardon@google.com, dave.hansen@linux.intel.com,
dmatlack@google.com, hpa@zytor.com, kvm@vger.kernel.org,
leitao@debian.org, linux-kernel@vger.kernel.org, maz@kernel.org,
mingo@redhat.com, mirsad.todorovac@alu.unizg.hr,
pawan.kumar.gupta@linux.intel.com, pbonzini@redhat.com,
peterz@infradead.org, shahuang@redhat.com, tabba@google.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: [BUG net-next] arch/x86/kernel/cpu/bugs.c:2935: "Unpatched return thunk in use. This should not happen!" [STACKTRACE]
Date: Wed, 3 Apr 2024 05:48:22 -0700 [thread overview]
Message-ID: <Zg1QFlDdRrLRZchi@google.com> (raw)
In-Reply-To: <20240403121436.GDZg1ILCn0a4Ddif3g@fat_crate.local>
On Wed, Apr 03, 2024, Borislav Petkov wrote:
> On Tue, Apr 02, 2024 at 08:38:56AM -0500, Michael Roth wrote:
> > On Tue, Apr 02, 2024 at 12:15:49PM +0200, bp@kernel.org wrote:
> > I can also trigger using one of the more basic KVM selftests:
> >
> > make INSTALL_HDR_PATH="$headers_dir" headers_install
> > make -C tools/testing/selftests TARGETS="kvm" EXTRA_CFLAGS="-DDEBUG -I$headers_dir"
> > sudo tools/testing/selftests/kvm/userspace_io_test
>
> Ok, thanks, that helped.
>
> Problem is:
>
> 7f4b5cde2409 ("kvm: Disable objtool frame pointer checking for vmenter.S")
>
> it is disabling checking of the arch/x86/kvm/svm/vmenter.S by objtool
> when CONFIG_FRAME_POINTER=y but that also leads to objtool *not*
> generating .return_sites and the return thunk remains unpatched.
>
> I think we need to say: ignore frame pointer checking but still generate
> .return_sites.
I'm guessing a general solution for OBJECT_FILES_NON_STANDARD is needed, but I
have a series to drop it for vmenter.S.
https://lore.kernel.org/all/20240223204233.3337324-9-seanjc@google.com
next prev parent reply other threads:[~2024-04-03 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 19:47 [BUG net-next] arch/x86/kernel/cpu/bugs.c:2935: "Unpatched return thunk in use. This should not happen!" [STACKTRACE] Mirsad Todorovac
2024-03-18 20:21 ` Borislav Petkov
2024-03-20 1:28 ` Mirsad Todorovac
2024-03-26 10:16 ` Borislav Petkov
2024-03-26 19:15 ` Mirsad Todorovac
2024-03-28 12:38 ` Michael Roth
2024-04-02 10:15 ` bp
2024-04-02 13:38 ` Michael Roth
2024-04-03 12:14 ` Borislav Petkov
2024-04-03 12:48 ` Sean Christopherson [this message]
2024-04-04 13:44 ` Borislav Petkov
2024-04-17 15:52 ` Paolo Bonzini
[not found] ` <f497a833-f945-4907-b916-1739324de014@alu.unizg.hr>
2024-04-04 13:41 ` Borislav Petkov
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=Zg1QFlDdRrLRZchi@google.com \
--to=seanjc@google.com \
--cc=bgardon@google.com \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=dmatlack@google.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=shahuang@redhat.com \
--cc=tabba@google.com \
--cc=tglx@linutronix.de \
--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.