From: Borislav Petkov <bp@alien8.de>
To: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: Michael Roth <michael.roth@amd.com>,
bp@kernel.org, bgardon@google.com, dave.hansen@linux.intel.com,
dmatlack@google.com, hpa@zytor.com, jpoimboe@kernel.org,
kvm@vger.kernel.org, leitao@debian.org,
linux-kernel@vger.kernel.org, maz@kernel.org, mingo@redhat.com,
pawan.kumar.gupta@linux.intel.com, pbonzini@redhat.com,
peterz@infradead.org, seanjc@google.com, 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: Thu, 4 Apr 2024 15:41:42 +0200 [thread overview]
Message-ID: <20240404134142.GCZg6uFh_ZSzUFLChd@fat_crate.local> (raw)
In-Reply-To: <f497a833-f945-4907-b916-1739324de014@alu.unizg.hr>
On Wed, Apr 03, 2024 at 03:43:02PM +0200, Mirsad Todorovac wrote:
> I wonder if I could make any additional contribution to the project.
I'd suggest:
https://kernel.org/doc/html/latest/process/2.Process.html#getting-started-with-kernel-development
and
https://kernel.org/doc/html/latest/process/development-process.html
which will give you a broader picture.
You could test linux-next, build random configs:
"make randconfig"
and see if you trigger a compiler warning, try to analyze it, understand
it and fix it.
It is a steep climb but it is a lot of fun. :-)
HTH.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2024-04-04 13:42 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
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 [this message]
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=20240404134142.GCZg6uFh_ZSzUFLChd@fat_crate.local \
--to=bp@alien8.de \
--cc=bgardon@google.com \
--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=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 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.