lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c4bc67dd-2a42-b318-7830-6741e3579775@gentwo.org>
Date: Wed, 25 Sep 2024 10:56:38 -0700 (PDT)
From: "Christoph Lameter (Ampere)" <cl@...two.org>
To: Ard Biesheuvel <ardb+git@...gle.com>
cc: linux-kernel@...r.kernel.org, Ard Biesheuvel <ardb@...nel.org>, 
    x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>, 
    Andy Lutomirski <luto@...nel.org>, Peter Zijlstra <peterz@...radead.org>, 
    Uros Bizjak <ubizjak@...il.com>, Dennis Zhou <dennis@...nel.org>, 
    Tejun Heo <tj@...nel.org>, 
    Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, 
    Paolo Bonzini <pbonzini@...hat.com>, 
    Vitaly Kuznetsov <vkuznets@...hat.com>, Juergen Gross <jgross@...e.com>, 
    Boris Ostrovsky <boris.ostrovsky@...cle.com>, 
    Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
    Arnd Bergmann <arnd@...db.de>, Masahiro Yamada <masahiroy@...nel.org>, 
    Kees Cook <kees@...nel.org>, Nathan Chancellor <nathan@...nel.org>, 
    Keith Packard <keithp@...thp.com>, Justin Stitt <justinstitt@...gle.com>, 
    Josh Poimboeuf <jpoimboe@...nel.org>, 
    Arnaldo Carvalho de Melo <acme@...nel.org>, 
    Namhyung Kim <namhyung@...nel.org>, Jiri Olsa <jolsa@...nel.org>, 
    Ian Rogers <irogers@...gle.com>, Adrian Hunter <adrian.hunter@...el.com>, 
    Kan Liang <kan.liang@...ux.intel.com>, linux-doc@...r.kernel.org, 
    linux-pm@...r.kernel.org, kvm@...r.kernel.org, 
    xen-devel@...ts.xenproject.org, linux-efi@...r.kernel.org, 
    linux-arch@...r.kernel.org, linux-sparse@...r.kernel.org, 
    linux-kbuild@...r.kernel.org, linux-perf-users@...r.kernel.org, 
    rust-for-linux@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [RFC PATCH 06/28] x86/percpu: Get rid of absolute per-CPU variable
 placement

On Wed, 25 Sep 2024, Ard Biesheuvel wrote:

> The x86_64 approach was needed to accommodate per-task stack protector
> cookies, which used to live at a fixed offset of GS+40, requiring GS to
> be treated as a base register. This is no longer the case, though, and
> so GS can be repurposed as a true per-CPU offset, adopting the same
> strategy as other architectures.
>
> This also removes the need for linker tricks to emit the per-CPU ELF
> segment at a different virtual address. It also means RIP-relative
> per-CPU variables no longer need to be relocated in the opposite
> direction when KASLR is applied, which was necessary because the 0x0
> based per-CPU region remains in place even when the kernel is moved
> around.

Looks like a good cleanup. Hope it does not break anything that relies on
structures %GS points to.

Reviewed-by: Christoph Lameter <cl@...ux.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ