[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ldxj7p22ze4ccoe4bmojhlabflw34t6jwyh24fklvessdyyial@w3fw6wwo7icp>
Date: Wed, 31 May 2023 17:05:46 +0200
From: Michal Koutný <mkoutny@...e.com>
To: Andrey Ryabinin <ryabinin.a.a@...il.com>
Cc: Dave Hansen <dave.hansen@...el.com>,
the arch/x86 maintainers <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Alexander Potapenko <glider@...gle.com>,
Andrey Konovalov <andreyknvl@...il.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Vincenzo Frascino <vincenzo.frascino@....com>,
kasan-dev@...glegroups.com, Kees Cook <keescook@...omium.org>,
Thomas Garnier <thgarnie@...gle.com>
Subject: Re: KASLR vs. KASAN on x86
On Mon, Mar 13, 2023 at 02:40:33PM +0100, Andrey Ryabinin <ryabinin.a.a@...il.com> wrote:
> Yes, with the vaddr_end = KASAN_SHADOW_START it should work,
> kaslr_memory_enabled() can be removed in favor of just the kaslr_enabled()
Thanks. FWIW, I've found the cautionary comment at vaddr_end from the
commit 1dddd2512511 ("x86/kaslr: Fix the vaddr_end mess"), so I'm not
removing kaslr_enabled_enabled() now.
Michal
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists