linux-kernel - Re: [PATCH 1/4] Move userspace syscall dispatch outside of common entry

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: <871r9k1dfi.ffs@nanos.tec.linutronix.de>
Date:   Wed, 02 Jun 2021 17:41:53 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     houdek.ryan@...-emu.org
Cc:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Ryan Houdek <Houdek.Ryan@...-emu.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH 1/4] Move userspace syscall dispatch outside of common entry

On Sat, May 29 2021 at 01:16, houdek ryan wrote:
> From: Ryan Houdek <Houdek.Ryan@...-emu.org>
>
> This will allow other architectures to support userspace syscall
> dispatch without supporting the syscall common entry.

NAK.

This is in common entry on purpose and won't go anywhere else. The every
arch has it's own broken entry code ordering mess needs to go away and
not proliferated further.

Move ARM to common entry first.

Thanks,

        tglx