[PATCH v4 1/4] syscalls: Restore address limit after a syscall · Thomas Garnier <hidden> · 2017-03-22
[PATCH v4 4/4] arm64/syscalls: Specific usage of verify_pre_usermode_state · Thomas Garnier <hidden> · 2017-03-22
[PATCH v4 3/4] arm/syscalls: Specific usage of verify_pre_usermode_state · Thomas Garnier <hidden> · 2017-03-22
[PATCH v4 2/4] x86/syscalls: Specific usage of verify_pre_usermode_state · Thomas Garnier <hidden> · 2017-03-22
Re: [PATCH v4 1/4] syscalls: Restore address limit after a syscall · Andy Lutomirski <luto@amacapital.net> · 2017-03-22
Re: [PATCH v4 1/4] syscalls: Restore address limit after a syscall · Thomas Garnier <hidden> · 2017-03-22
Re: [PATCH v4 1/4] syscalls: Restore address limit after a syscall · "H. Peter Anvin" <hpa@zytor.com> · 2017-03-22
Re: [PATCH v4 1/4] syscalls: Restore address limit after a syscall · Thomas Garnier <hidden> · 2017-03-23
Re: [PATCH v4 1/4] syscalls: Restore address limit after a syscall · Borislav Petkov <bp@alien8.de> · 2017-03-23
Re: [PATCH v4 1/4] syscalls: Restore address limit after a syscall · Thomas Garnier <hidden> · 2017-03-23
Re: [PATCH v4 1/4] syscalls: Restore address limit after a syscall · "H. Peter Anvin" <hpa@zytor.com> · 2017-03-22

Re: [PATCH v4 1/4] syscalls: Restore address limit after a syscall

From: "H. Peter Anvin" <hpa@zytor.com>
Date: 2017-03-22 21:17:42
Also in: linux-arm-kernel, linux-s390, lkml

On 03/22/17 13:49, Thomas Garnier wrote:

We can default to BUGging. I think my approach was avoiding doing a
BUG_ON just to avoid breaking people.

Breaking on a potentially-exploitable bug is a feature.

	-hpa