From: Breno Leitao <leitao@debian.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
usamaarif642@gmail.com, rmikey@meta.com, andreyknvl@gmail.com,
kasan-dev@googlegroups.com, linux-efi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH] arm64: efi: Fix KASAN false positive for EFI runtime stack
Date: Mon, 7 Jul 2025 09:08:49 -0700 [thread overview]
Message-ID: <aGvxEYDP8pVlalaz@gmail.com> (raw)
In-Reply-To: <aGsYkFnHEkn0dBsW@arm.com>
On Sun, Jul 06, 2025 at 07:45:04PM -0500, Catalin Marinas wrote:
> On Fri, Jul 04, 2025 at 02:40:17PM +0100, Mark Rutland wrote:
> > On Fri, Jul 04, 2025 at 02:33:35PM +0100, Will Deacon wrote:
> > > I would actually like to select VMAP_STACK unconditionally for arm64.
> > > Historically, we were held back waiting for all the various KASAN modes
> > > to support vmalloc properly, but I _think_ that's fixed now...
> > >
> > > The VMAP_STACK dependency is:
> > >
> > > depends on !KASAN || KASAN_HW_TAGS || KASAN_VMALLOC
> > >
> > > and in arm64 we have:
> > >
> > > select KASAN_VMALLOC if KASAN
> > >
> > > so it should be fine to select it afaict.
> > >
> > > Any reason not to do that?
> >
> > Not that I am aware of.
> >
> > I'm also in favour of unconditionally selecting VMAP_STACK.
>
> So am I.
Thanks. I've played a bit with it, and did some mechanical work, and
send a v1.
https://lore.kernel.org/all/20250707-arm64_vmap-v1-0-8de98ca0f91c@debian.org/
prev parent reply other threads:[~2025-07-07 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 12:55 [PATCH] arm64: efi: Fix KASAN false positive for EFI runtime stack Breno Leitao
2025-07-03 16:35 ` Catalin Marinas
2025-07-04 8:26 ` Ard Biesheuvel
2025-07-04 12:36 ` Breno Leitao
2025-07-04 13:33 ` Will Deacon
2025-07-04 13:37 ` Ard Biesheuvel
2025-07-04 13:40 ` Mark Rutland
2025-07-07 0:45 ` Catalin Marinas
2025-07-07 16:08 ` Breno Leitao [this message]
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=aGvxEYDP8pVlalaz@gmail.com \
--to=leitao@debian.org \
--cc=andreyknvl@gmail.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@meta.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rmikey@meta.com \
--cc=usamaarif642@gmail.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).