linux-kernel - Q: does force_iret() make any sense today?

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

Message-ID: <20191218153107.GA3489@redhat.com>
Date:   Wed, 18 Dec 2019 16:31:07 +0100
From:   Oleg Nesterov <oleg@...hat.com>
To:     Andy Lutomirski <luto@...nel.org>, Borislav Petkov <bp@...en8.de>,
        Brian Gerst <brgerst@...il.com>,
        Ingo Molnar <mingo@...hat.com>, Peter Anvin <hpa@...or.com>
Cc:     linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Q: does force_iret() make any sense today?

I do not pretend I understand the arch/x86/entry/ code, but it seems that
asm does all the necessary checks and the "extra" TIF_NOTIFY_RESUME simply
has no effect except tracehook_notify_resume() will be called for no reason?

Oleg.