From: Borislav Petkov <bp@alien8.de>
To: 1sh1ro <yangguikun19@qq.com>
Cc: Ihor Solodrai <ihor.solodrai@linux.dev>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Alexander Potapenko <glider@google.com>,
Thomas Gleixner <tglx@kernel.org>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] kasan: Fix false-positive wild-memory-access on x86 under 5-level paging
Date: Mon, 12 Oct 2026 12:21:06 -0700 [thread overview]
Message-ID: <20261012192106.GAas0zIsS_fb6dgtGB@fat_crate.local> (raw)
In-Reply-To: <tencent_8BA9ABDFF623474ECBA6E251A03E19512808@qq.com>
On Tue, Oct 13, 2026 at 02:06:08AM +0800, 1sh1ro wrote:
> I hit the same false positive and can add a data point that seems relevant for
> the fix: it still reproduces on 7.3-rc5, i.e. after the CPUID rewrite that was
> expected to take care of it. The rewrite is in 7.3 -- get_cpu_cap() became
> cpu_detect() -- and that is exactly the function my crashes interrupt.
I don't know which rewrite you mean.
If you mean those patches by Ihor:
2711d67bc3a7 x86/cpu: Don't transiently clear the boot CPU's capabilities
db349783ca7a x86/cpu: Move 32-bit SEP setup into identify_cpu()
ad86fe2134cc x86/cpu: Inline generic_identify() into identify_cpu()
7a762b51a149 x86/cpu: Initialize boot CPU cpuinfo defaults early
54a2882ab9f7 x86/cpu: Factor init_cpu_info() out of identify_cpu()
they're in tip queued for 7.4. So not mainline yet.
You can test current tip/master if you mean them.
HTH.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-10-12 19:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 17:56 Ihor Solodrai
2026-06-10 18:39 ` Andrey Konovalov
2026-06-10 21:55 ` Ihor Solodrai
2026-06-12 16:30 ` Kiryl Shutsemau
2026-06-12 19:42 ` Ihor Solodrai
2026-06-17 22:13 ` Ihor Solodrai
2026-06-18 16:55 ` Andrey Ryabinin
2026-06-18 17:09 ` Borislav Petkov
2026-06-18 18:12 ` Dave Hansen
2026-06-18 18:38 ` Borislav Petkov
2026-06-23 0:29 ` Ihor Solodrai
2026-06-24 2:57 ` Borislav Petkov
2026-06-24 22:45 ` Ihor Solodrai
2026-06-24 23:45 ` Borislav Petkov
[not found] ` <20261013015904.44144-kasan-early-boot@yangguikun19.qq.com>
2026-10-12 18:06 ` 1sh1ro
2026-10-12 19:21 ` Borislav Petkov [this message]
2026-06-23 0:35 ` Ihor Solodrai
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=20261012192106.GAas0zIsS_fb6dgtGB@fat_crate.local \
--to=bp@alien8.de \
--cc=andreyknvl@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=ihor.solodrai@linux.dev \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryabinin.a.a@gmail.com \
--cc=tglx@kernel.org \
--cc=yangguikun19@qq.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
all inboxes | Powered by JetHome®