From: Borislav Petkov <bp@alien8.de>
To: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: x86@kernel.org, Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Fuad Tabba <tabba@google.com>,
Marc Zyngier <maz@kernel.org>,
Shaoqin Huang <shahuang@redhat.com>,
David Matlack <dmatlack@google.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Breno Leitao <leitao@debian.org>,
kvm@vger.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: Mon, 18 Mar 2024 21:21:24 +0100 [thread overview]
Message-ID: <20240318202124.GCZfiiRGVV0angYI9j@fat_crate.local> (raw)
In-Reply-To: <1d10cd73-2ae7-42d5-a318-2f9facc42bbe@alu.unizg.hr>
On Mon, Mar 18, 2024 at 08:47:26PM +0100, Mirsad Todorovac wrote:
> With the latest net-next v6.8-5204-g237bb5f7f7f5 kernel, while running kselftest, there was this
> trap and stacktrace:
Send your kernel .config and how exactly you're triggering it, please.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-03-18 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 19:47 Mirsad Todorovac
2024-03-18 20:21 ` Borislav Petkov [this message]
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
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=20240318202124.GCZfiiRGVV0angYI9j@fat_crate.local \
--to=bp@alien8.de \
--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=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=seanjc@google.com \
--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 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®