From: Brendan Jackman <jackmanb@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Brendan Jackman <jackmanb@google.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Marco Elver <elver@google.com>, Ard Biesheuvel <ardb@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
<kasan-dev@googlegroups.com>, <linux-kernel@vger.kernel.org>,
<llvm@lists.linux.dev>
Subject: Re: [PATCH v3 1/3] kasan: mark !__SANITIZE_ADDRESS__ stubs __always_inline
Date: Fri, 19 Dec 2025 11:45:01 +0000 [thread overview]
Message-ID: <DF261MXQUYYU.130N0WZE4DP4U@google.com> (raw)
In-Reply-To: <20251218092439.GL3707891@noisy.programming.kicks-ass.net>
>>
>> So in the meantime what's the cleanest fix? Going straight to the arch_*
>> calls from SEV seems pretty yucky in its own right.
>
> This is what I would do (and have done in the past):
>
> 14d3b376b6c3 ("x86/entry, cpumask: Provide non-instrumented variant of cpu_is_offline()")
> f5c54f77b07b ("cpumask: Add a x86-specific cpumask_clear_cpu() helper")
OK, let's do it this way then.
>> > For the short term, we could avoid this by using arch___set_bit()
>
> arch_set_bit(), right?
I don't think so. Currently the GHCB accessors ar using __set_bit() i.e.
the non-atomic version. Am I missing something?
next prev parent reply other threads:[~2025-12-19 11:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 10:16 [PATCH v3 0/3] Noinstr fixes for K[CA]SAN with GCOV Brendan Jackman
2025-12-16 10:16 ` [PATCH v3 1/3] kasan: mark !__SANITIZE_ADDRESS__ stubs __always_inline Brendan Jackman
2025-12-16 13:01 ` Peter Zijlstra
2025-12-17 13:53 ` Brendan Jackman
2025-12-18 9:24 ` Peter Zijlstra
2025-12-19 11:45 ` Brendan Jackman [this message]
2026-01-04 6:07 ` Borislav Petkov
2025-12-16 10:16 ` [PATCH v3 2/3] kcsan: mark !__SANITIZE_THREAD__ " Brendan Jackman
2025-12-16 10:16 ` [PATCH v3 3/3] x86/sev: Disable GCOV on noinstr object Brendan Jackman
2026-01-05 9:47 ` [tip: x86/urgent] " tip-bot2 for Brendan Jackman
2025-12-16 10:18 ` [PATCH v3 0/3] Noinstr fixes for K[CA]SAN with GCOV Marco Elver
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=DF261MXQUYYU.130N0WZE4DP4U@google.com \
--to=jackmanb@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=justinstitt@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=peterz@infradead.org \
--cc=ryabinin.a.a@gmail.com \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--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