linux-kernel - Re: [RFC PATCH 0/3] Enable strict percpu address space checks

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] [day] [month] [year] [list]

Message-ID: <CAFULd4a+n4+t4rCTpsyvjd=tNfB-O_c0y9+tF-re1WJPz4JJrw@mail.gmail.com>
Date: Mon, 12 Aug 2024 16:41:53 +0200
From: Uros Bizjak <ubizjak@...il.com>
To: "Christoph Lameter (Ampere)" <cl@...two.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org, 
	Dennis Zhou <dennis@...nel.org>, Tejun Heo <tj@...nel.org>, Andy Lutomirski <luto@...nel.org>, 
	Ingo Molnar <mingo@...nel.org>, Nadav Amit <nadav.amit@...il.com>, Brian Gerst <brgerst@...il.com>, 
	Denys Vlasenko <dvlasenk@...hat.com>, "H . Peter Anvin" <hpa@...or.com>, 
	Linus Torvalds <torvalds@...ux-foundation.org>, Peter Zijlstra <peterz@...radead.org>, 
	Thomas Gleixner <tglx@...utronix.de>, Borislav Petkov <bp@...en8.de>, 
	Luc Van Oostenryck <luc.vanoostenryck@...il.com>
Subject: Re: [RFC PATCH 0/3] Enable strict percpu address space checks

On Tue, Aug 6, 2024 at 10:32 PM Christoph Lameter (Ampere)
<cl@...two.org> wrote:
>
> On Mon, 5 Aug 2024, Uros Bizjak wrote:
>
> > Also, the last patch hijacks __percpu tag and repurposes it as a named
> > address space qualifier. While this works surprisingly well in this RFC
> > patchset, I would really appreciate some help on how to rewrite this
> > hack into some "production ready" code.
>
> This looks like good work to find issues with per cpu macro usage. Per cpu
> macros are a bit esoteric and it would be a good benefit if you can
> get this done.

Thanks, I will do my best.

> Sadly I cannot help you much with the address space qualifier.

I have solved this in RFC v2, please see [1].

[1] https://lore.kernel.org/lkml/20240812115945.484051-1-ubizjak@gmail.com/

Thanks and best regards,
Uros.