[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+fCnZci8YK04PPMT7gkMrrNHbMB3Ks+D4xG-5XkEOaywyrGhw@mail.gmail.com>
Date: Tue, 13 Jan 2026 02:47:13 +0100
From: Andrey Konovalov <andreyknvl@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Maciej Wieczór-Retman <m.wieczorretman@...me>
Cc: corbet@....net, morbo@...gle.com, rppt@...nel.org,
lorenzo.stoakes@...cle.com, ubizjak@...il.com, mingo@...hat.com,
vincenzo.frascino@....com, maciej.wieczor-retman@...el.com, maz@...nel.org,
catalin.marinas@....com, yeoreum.yun@....com, will@...nel.org,
jackmanb@...gle.com, samuel.holland@...ive.com, glider@...gle.com,
osandov@...com, nsc@...nel.org, luto@...nel.org, jpoimboe@...nel.org,
Liam.Howlett@...cle.com, kees@...nel.org, jan.kiszka@...mens.com,
thomas.lendacky@....com, jeremy.linton@....com, dvyukov@...gle.com,
axelrasmussen@...gle.com, leitao@...ian.org, ryabinin.a.a@...il.com,
bigeasy@...utronix.de, peterz@...radead.org, mark.rutland@....com,
urezki@...il.com, brgerst@...il.com, hpa@...or.com, mhocko@...e.com,
weixugc@...gle.com, kbingham@...nel.org, vbabka@...e.cz, nathan@...nel.org,
trintaeoitogc@...il.com, samitolvanen@...gle.com, tglx@...nel.org,
thuth@...hat.com, surenb@...gle.com, anshuman.khandual@....com,
smostafa@...gle.com, yuanchu@...gle.com, ada.coupriediaz@....com,
dave.hansen@...ux.intel.com, kas@...nel.org, nick.desaulniers+lkml@...il.com,
david@...nel.org, bp@...en8.de, ardb@...nel.org, justinstitt@...gle.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, kasan-dev@...glegroups.com,
llvm@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-doc@...r.kernel.org, linux-kbuild@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH v8 00/14] kasan: x86: arm64: KASAN tag-based mode for x86
On Mon, Jan 12, 2026 at 9:53 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Mon, 12 Jan 2026 20:08:23 +0000 Maciej Wieczór-Retman <m.wieczorretman@...me> wrote:
>
> > >OK, known issues and they are understandable. With this patchset is
> > >there any way in which our testers can encounter these things? If so
> > >can we make changes to protect them from hitting known issues?
> >
> > The gcc documentation states that the -fsanitize=kernel-hwaddress is
> > similar to -fsanitize=hwaddress, which only works on AArch64. So that
> > hints that it shouldn't work.
> >
> > But while with KASAN sw_tags enabled the kernel compiles fine with gcc,
> > at least in my patched qemu it doesn't run. I remember Ada Couprie Diaz
> > mention that passing -march=arrowlake might help since the tag support
> > seems to be based on arch.
FYI, there are some known GCC issues with arm64 SW_TAGS mode as well:
https://bugzilla.kernel.org/show_bug.cgi?id=218043#c3.
> >
> > I'll check if there's a non-hacky way to have gcc work too, but perhaps
> > to minimize hitting known issue, for now HAVE_ARCH_KASAN_SW_TAGS should
> > be locked behind both ADDRESS_MASKING and CC_IS_CLANG in the Kconfig?
>
> Yes please - my main concern is that we avoid causing any disruption to
> testers/buildbots/fuzzers/etc.
I left some comments, but from my/KASAN point of view, the series is
ready for linux-next (but this could wait for a week and maybe the
next version of the series).
I wouldn't think there would be disruption issues: one would need to
deliberately enable the SW_TAGS mode for x86 (as GENERIC is the
default mode when just enabling KASAN). But I don't mind locking down
x86 SW_TAGS to be Clang-only for now if GCC is known not to work at
all.
Powered by blists - more mailing lists