linux-kernel - Re: [PATCH v2 14/36] x86/entry/64/compat: Disable SYSENTER and SYSCALL32 entries

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: <20151008154111.GB24052@nazgul.tnic>
Date:	Thu, 8 Oct 2015 17:41:11 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Andy Lutomirski <luto@...nel.org>
Cc:	x86@...nel.org, linux-kernel@...r.kernel.org,
	Brian Gerst <brgerst@...il.com>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v2 14/36] x86/entry/64/compat: Disable SYSENTER and
 SYSCALL32 entries

On Mon, Oct 05, 2015 at 05:48:02PM -0700, Andy Lutomirski wrote:
> We've disabled the vDSO helpers to call them, so turn off the
> entries entirely (temporarily) in preparation for cleaning them up.
> 
> Signed-off-by: Andy Lutomirski <luto@...nel.org>
> ---
>  arch/x86/entry/entry_64_compat.S | 13 +++++++++++++
>  1 file changed, 13 insertions(+)

What do we say for the case when someone bisects, lands at this patch
and, as Murphy would generally do it, has a reproducer which is calling
SYSENTER/SYSCALL32?

Tough luck?

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/