From: Nikolay Borisov <nik.borisov@suse.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Marco Elver <elver@google.com>,
kasan-dev@googlegroups.com
Subject: Re: Unpatched return thunk in use. This should not happen!
Date: Tue, 26 Mar 2024 16:08:32 +0200 [thread overview]
Message-ID: <47e032a0-c9a0-4639-867b-cb3d67076eaf@suse.com> (raw)
In-Reply-To: <0851a207-7143-417e-be31-8bf2b3afb57d@molgen.mpg.de>
On 26.03.24 г. 14:40 ч., Paul Menzel wrote:
> Dear Linux folks,
>
>
> On a Dell XPS 13 9360/0596KF, BIOS 2.21.0 06/02/2022, Linux 6.9-rc1+
> built with
>
> CONFIG_KCSAN=y
>
So the problem happens when KCSAN=y CONFIG_CONSTRUCTORS is also enabled
and this results in an indirect call in do_mod_ctors():
mod->ctors[i]();
When KCSAN is disabled, do_mod_ctors is empty, hence the warning is not
printed.
next prev parent reply other threads:[~2024-03-26 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 12:40 Paul Menzel
2024-03-26 12:49 ` Borislav Petkov
2024-03-26 12:56 ` Paul Menzel
2024-03-26 14:08 ` Nikolay Borisov [this message]
2024-03-26 15:52 ` Borislav Petkov
2024-03-26 16:04 ` Nikolay Borisov
2024-03-26 19:12 ` Borislav Petkov
2024-03-26 19:33 ` Marco Elver
2024-03-26 20:25 ` [PATCH] kbuild: Disable KCSAN for autogenerated *.mod.c intermediaries Borislav Petkov
2024-03-26 20:41 ` Marco Elver
2024-03-27 6:31 ` Nikolay Borisov
2024-03-28 6:07 ` Paul Menzel
2024-03-30 22:32 ` Masahiro Yamada
2024-03-30 22:48 ` Borislav Petkov
2025-03-25 20:55 Unpatched return thunk in use. This should not happen! Heiner Kallweit
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=47e032a0-c9a0-4639-867b-cb3d67076eaf@suse.com \
--to=nik.borisov@suse.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=elver@google.com \
--cc=jpoimboe@kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pmenzel@molgen.mpg.de \
--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®