From: Maciej Wieczor-Retman <m.wieczorretman@pm.me>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: urezki@gmail.com, ryan.roberts@arm.com, kevin.brodsky@arm.com,
samuel.holland@sifive.com, dave.hansen@linux.intel.com,
jeremy.linton@arm.com, peterz@infradead.org, weixugc@google.com,
ljs@kernel.org, ryabinin.a.a@gmail.com, rppt@kernel.org,
bp@alien8.de, luto@kernel.org, jan.kiszka@siemens.com,
mingo@redhat.com, david@kernel.org, mhocko@suse.com,
andreas@gaisler.com, kas@kernel.org, Liam.Howlett@oracle.com,
morbo@google.com, thuth@redhat.com, catalin.marinas@arm.com,
ankur.a.arora@oracle.com, kbingham@kernel.org,
nick.desaulniers+lkml@gmail.com, andreyknvl@gmail.com,
dvyukov@google.com, corbet@lwn.net, leitao@debian.org,
hpa@zytor.com, tglx@kernel.org, yuanchu@google.com,
ardb@kernel.org, vincenzo.frascino@arm.com, tabba@google.com,
joey.gouly@arm.com, nsc@kernel.org, will@kernel.org,
yeoreum.yun@arm.com, nathan@kernel.org,
maciej.wieczor-retman@intel.com, skhan@linuxfoundation.org,
axelrasmussen@google.com, osandov@fb.com, surenb@google.com,
justinstitt@google.com, kees@kernel.org, vbabka@kernel.org,
hsj0512@snu.ac.kr, trintaeoitogc@gmail.com, jackmanb@google.com,
maz@kernel.org, glider@google.com, linux-doc@vger.kernel.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
kasan-dev@googlegroups.com, workflows@vger.kernel.org,
llvm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kbuild@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v11 00/15] kasan: x86: arm64: KASAN tag-based mode for x86
Date: Tue, 10 Mar 2026 19:17:43 +0000 [thread overview]
Message-ID: <abBpbS3tplFSlVgx@wieczorr-mobl1.localdomain> (raw)
In-Reply-To: <20260310112421.8ceb7415e14b49cbd86db715@linux-foundation.org>
On 2026-03-10 at 11:24:21 -0700, Andrew Morton wrote:
>On Tue, 10 Mar 2026 17:51:19 +0000 Maciej Wieczor-Retman <m.wieczorretman@pm.me> wrote:
>
>>
>> [1] Currently inline mode doesn't work on x86 due to things missing in
>> the compiler. I have written a patch for clang that seems to fix the
>> inline mode and I was able to boot and check that all patches regarding
>> the inline mode work as expected. My hope is to post the patch to LLVM
>> once this series is completed, and then make inline mode available in
>> the kernel config.
>>
>> [2] While I was able to boot the inline tag-based kernel with my
>> compiler changes in a simulated environment, due to toolchain
>> difficulties I couldn't get it to boot on the machine I had access to.
>> Also boot time results from the simulation seem too good to be true, and
>> they're much too worse for the generic case to be believable. Therefore
>> I'm posting only results from the physical server platform.
>>
>> ======= Compilation
>> Clang was used to compile the series (make LLVM=1) since gcc doesn't
>> seem to have support for KASAN tag-based compiler instrumentation on
>> x86. Patchset does seem to compile with gcc without an issue but doesn't
>> boot afterwards.
>
>So LLVM works partially and gcc doesn't work at all?
The non-working options are disabled in Kconfig so right now only outline KASAN
with LLVM works fully.
>Do we know which compiler people are using? Google tells me that
>Android, ChromeOS, and OpenMandriva use LLVM. That's pretty thin.
I don't have any numbers on this matter, from working on this I only got that
there is much more KASAN traffic around clang. So I thought that most KASAN
users prefer LLVM.
>This is all rather problematic and it isn't clear (to me) how to
>proceed at this time. Do we have any projections on when all this will
>be fixed up?
My understanding is that there is something off in gcc support. I recall Andrey
Konovalov mentioning that gcc also doesn't work well with arm64's KASAN
tag-based mode. As for LLVM inline support I do know the codebase a bit so I got
some WIP patches there. But I wanted to see where this review process goes
before posting to LLVM.
>> The series is based on mm-new.
>
>I actually carry kexec patches in the mm-nonmm-[un]stable branches.
>But the series applies OK anyway.
Should I base this patchset on top of mm-nonmm-stable in the future? I was after
one patch by Andrey Ryabinin that was in mm-new and I needed to rebase on top of
it.
--
Kind regards
Maciej Wieczór-Retman
next prev parent reply other threads:[~2026-03-10 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 17:51 Maciej Wieczor-Retman
2026-03-10 17:53 ` [PATCH v11 01/15] kasan: sw_tags: Use arithmetic shift for shadow computation Maciej Wieczor-Retman
2026-03-10 17:55 ` [PATCH v11 15/15] docs: Update KASAN and x86 memory map documentations Maciej Wieczor-Retman
2026-03-10 18:24 ` [PATCH v11 00/15] kasan: x86: arm64: KASAN tag-based mode for x86 Andrew Morton
2026-03-10 19:17 ` Maciej Wieczor-Retman [this message]
2026-03-10 19:00 ` Peter Zijlstra
2026-03-10 19:30 ` Maciej Wieczor-Retman
2026-03-11 11:05 ` Peter Zijlstra
2026-03-11 11:13 ` Maciej Wieczor-Retman
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=abBpbS3tplFSlVgx@wieczorr-mobl1.localdomain \
--to=m.wieczorretman@pm.me \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=andreyknvl@gmail.com \
--cc=ankur.a.arora@oracle.com \
--cc=ardb@kernel.org \
--cc=axelrasmussen@google.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=hsj0512@snu.ac.kr \
--cc=jackmanb@google.com \
--cc=jan.kiszka@siemens.com \
--cc=jeremy.linton@arm.com \
--cc=joey.gouly@arm.com \
--cc=justinstitt@google.com \
--cc=kas@kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=kbingham@kernel.org \
--cc=kees@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luto@kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=maz@kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nsc@kernel.org \
--cc=osandov@fb.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=samuel.holland@sifive.com \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=tabba@google.com \
--cc=tglx@kernel.org \
--cc=thuth@redhat.com \
--cc=trintaeoitogc@gmail.com \
--cc=urezki@gmail.com \
--cc=vbabka@kernel.org \
--cc=vincenzo.frascino@arm.com \
--cc=weixugc@google.com \
--cc=will@kernel.org \
--cc=workflows@vger.kernel.org \
--cc=x86@kernel.org \
--cc=yeoreum.yun@arm.com \
--cc=yuanchu@google.com \
/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