linux-kernel - Re: [PATCH] x86/entry: Clarify the RF saving/restoring situation with SYSCALL/SYSRET

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: <20160803175412.GE2590@nazgul.tnic>
Date:	Wed, 3 Aug 2016 19:54:12 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/entry: Clarify the RF saving/restoring situation
 with SYSCALL/SYSRET

On Wed, Aug 03, 2016 at 10:24:18AM -0700, Andy Lutomirski wrote:
> AFAICT the AMD people didn't think of any use cases involving doing
> anything interesting between SYSCALL and SYSRET.  Witness the
> sysret_ss_attrs goof, for example: apparently SYSCALL; context switch;
> IRET; interrupt; context switch; SYSRET didn't occur to AMD as a valid
> use case.

/me hands Andy a time machine to go fix this properly, before so much
silicon ships.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--