Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Mon, Nov 13, 2017 at 1:07 PM, Dave Hansen wrote: > On 11/12/2017 07:52 PM, Andy Lutomirski wrote: >> On Fri, Nov 10, 2017 at 3:04 PM, Dave Hansen >> wrote: >>> On 11/10/2017 02:06 PM, Andy Lutomirski wrote: I have nothing against

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Mon, Nov 13, 2017 at 1:07 PM, Dave Hansen wrote: > On 11/12/2017 07:52 PM, Andy Lutomirski wrote: >> On Fri, Nov 10, 2017 at 3:04 PM, Dave Hansen >> wrote: >>> On 11/10/2017 02:06 PM, Andy Lutomirski wrote: I have nothing against disabling native. I object to breaking the weird

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/12/2017 07:52 PM, Andy Lutomirski wrote: > On Fri, Nov 10, 2017 at 3:04 PM, Dave Hansen > wrote: >> On 11/10/2017 02:06 PM, Andy Lutomirski wrote: >>> I have nothing against disabling native. I object to breaking the >>> weird binary tracing behavior in the

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/12/2017 07:52 PM, Andy Lutomirski wrote: > On Fri, Nov 10, 2017 at 3:04 PM, Dave Hansen > wrote: >> On 11/10/2017 02:06 PM, Andy Lutomirski wrote: >>> I have nothing against disabling native. I object to breaking the >>> weird binary tracing behavior in the emulation mode, especially if

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Fri, Nov 10, 2017 at 3:04 PM, Dave Hansen wrote: > On 11/10/2017 02:06 PM, Andy Lutomirski wrote: >> On Thu, Nov 9, 2017 at 10:31 PM, Dave Hansen >> wrote: >>> On 11/09/2017 06:25 PM, Andy Lutomirski wrote: Here are two proposals

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Fri, Nov 10, 2017 at 3:04 PM, Dave Hansen wrote: > On 11/10/2017 02:06 PM, Andy Lutomirski wrote: >> On Thu, Nov 9, 2017 at 10:31 PM, Dave Hansen >> wrote: >>> On 11/09/2017 06:25 PM, Andy Lutomirski wrote: Here are two proposals to address this without breaking vsyscalls. 1.

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/10/2017 02:06 PM, Andy Lutomirski wrote: > On Thu, Nov 9, 2017 at 10:31 PM, Dave Hansen > wrote: >> On 11/09/2017 06:25 PM, Andy Lutomirski wrote: >>> Here are two proposals to address this without breaking vsyscalls. >>> >>> 1. Set NX on low mappings that are

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/10/2017 02:06 PM, Andy Lutomirski wrote: > On Thu, Nov 9, 2017 at 10:31 PM, Dave Hansen > wrote: >> On 11/09/2017 06:25 PM, Andy Lutomirski wrote: >>> Here are two proposals to address this without breaking vsyscalls. >>> >>> 1. Set NX on low mappings that are _PAGE_USER. Don't set NX on

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Thu, Nov 9, 2017 at 10:31 PM, Dave Hansen wrote: > On 11/09/2017 06:25 PM, Andy Lutomirski wrote: >> Here are two proposals to address this without breaking vsyscalls. >> >> 1. Set NX on low mappings that are _PAGE_USER. Don't set NX on high >> mappings but,

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Thu, Nov 9, 2017 at 10:31 PM, Dave Hansen wrote: > On 11/09/2017 06:25 PM, Andy Lutomirski wrote: >> Here are two proposals to address this without breaking vsyscalls. >> >> 1. Set NX on low mappings that are _PAGE_USER. Don't set NX on high >> mappings but, optionally, warn if you see

[PATCH 24/30] x86, kaiser: disable native VSYSCALL

From: Dave Hansen The KAISER code attempts to "poison" the user portion of the kernel page tables. It detects entries that it wants that it wants to poison in two ways: * Looking for addresses >= PAGE_OFFSET * Looking for entries without _PAGE_USER set But, to

[PATCH 24/30] x86, kaiser: disable native VSYSCALL

From: Dave Hansen The KAISER code attempts to "poison" the user portion of the kernel page tables. It detects entries that it wants that it wants to poison in two ways: * Looking for addresses >= PAGE_OFFSET * Looking for entries without _PAGE_USER set But, to allow the _PAGE_USER check to

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/09/2017 06:25 PM, Andy Lutomirski wrote: > Here are two proposals to address this without breaking vsyscalls. > > 1. Set NX on low mappings that are _PAGE_USER. Don't set NX on high > mappings but, optionally, warn if you see _PAGE_USER on any address > that isn't the vsyscall page. > >

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/09/2017 06:25 PM, Andy Lutomirski wrote: > Here are two proposals to address this without breaking vsyscalls. > > 1. Set NX on low mappings that are _PAGE_USER. Don't set NX on high > mappings but, optionally, warn if you see _PAGE_USER on any address > that isn't the vsyscall page. > >

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Thu, Nov 9, 2017 at 5:22 PM, Dave Hansen wrote: > On 11/09/2017 05:04 PM, Andy Lutomirski wrote: >> On Thu, Nov 9, 2017 at 4:57 PM, Dave Hansen >> wrote: >>> On 11/09/2017 04:53 PM, Andy Lutomirski wrote: > The KAISER code

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Thu, Nov 9, 2017 at 5:22 PM, Dave Hansen wrote: > On 11/09/2017 05:04 PM, Andy Lutomirski wrote: >> On Thu, Nov 9, 2017 at 4:57 PM, Dave Hansen >> wrote: >>> On 11/09/2017 04:53 PM, Andy Lutomirski wrote: > The KAISER code attempts to "poison" the user portion of the kernel page >

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/09/2017 05:04 PM, Andy Lutomirski wrote: > On Thu, Nov 9, 2017 at 4:57 PM, Dave Hansen > wrote: >> On 11/09/2017 04:53 PM, Andy Lutomirski wrote: The KAISER code attempts to "poison" the user portion of the kernel page tables. It detects the entries

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/09/2017 05:04 PM, Andy Lutomirski wrote: > On Thu, Nov 9, 2017 at 4:57 PM, Dave Hansen > wrote: >> On 11/09/2017 04:53 PM, Andy Lutomirski wrote: The KAISER code attempts to "poison" the user portion of the kernel page tables. It detects the entries pages that it wants that it

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Thu, Nov 9, 2017 at 4:57 PM, Dave Hansen wrote: > On 11/09/2017 04:53 PM, Andy Lutomirski wrote: >>> The KAISER code attempts to "poison" the user portion of the kernel page >>> tables. It detects the entries pages that it wants that it wants to >>> poison in two

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Thu, Nov 9, 2017 at 4:57 PM, Dave Hansen wrote: > On 11/09/2017 04:53 PM, Andy Lutomirski wrote: >>> The KAISER code attempts to "poison" the user portion of the kernel page >>> tables. It detects the entries pages that it wants that it wants to >>> poison in two ways: >>> * Looking for

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/09/2017 04:53 PM, Andy Lutomirski wrote: >> The KAISER code attempts to "poison" the user portion of the kernel page >> tables. It detects the entries pages that it wants that it wants to >> poison in two ways: >> * Looking for addresses >= PAGE_OFFSET >> * Looking for entries without

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/09/2017 04:53 PM, Andy Lutomirski wrote: >> The KAISER code attempts to "poison" the user portion of the kernel page >> tables. It detects the entries pages that it wants that it wants to >> poison in two ways: >> * Looking for addresses >= PAGE_OFFSET >> * Looking for entries without

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Thu, Nov 9, 2017 at 11:26 AM, Dave Hansen wrote: > On 11/09/2017 11:04 AM, Andy Lutomirski wrote: >> On Wed, Nov 8, 2017 at 11:47 AM, Dave Hansen >> wrote: >>> >>> From: Dave Hansen >>> >>> The VSYSCALL

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Thu, Nov 9, 2017 at 11:26 AM, Dave Hansen wrote: > On 11/09/2017 11:04 AM, Andy Lutomirski wrote: >> On Wed, Nov 8, 2017 at 11:47 AM, Dave Hansen >> wrote: >>> >>> From: Dave Hansen >>> >>> The VSYSCALL page is mapped by kernel page tables at a kernel address. >>> It is troublesome to

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/09/2017 11:04 AM, Andy Lutomirski wrote: > On Wed, Nov 8, 2017 at 11:47 AM, Dave Hansen > wrote: >> >> From: Dave Hansen >> >> The VSYSCALL page is mapped by kernel page tables at a kernel address. >> It is troublesome to support

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On 11/09/2017 11:04 AM, Andy Lutomirski wrote: > On Wed, Nov 8, 2017 at 11:47 AM, Dave Hansen > wrote: >> >> From: Dave Hansen >> >> The VSYSCALL page is mapped by kernel page tables at a kernel address. >> It is troublesome to support with KAISER in place, so disable the >> native case. >> >>

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Wed, Nov 8, 2017 at 11:47 AM, Dave Hansen wrote: > > From: Dave Hansen > > The VSYSCALL page is mapped by kernel page tables at a kernel address. > It is troublesome to support with KAISER in place, so disable the > native case. > >

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Wed, Nov 8, 2017 at 11:47 AM, Dave Hansen wrote: > > From: Dave Hansen > > The VSYSCALL page is mapped by kernel page tables at a kernel address. > It is troublesome to support with KAISER in place, so disable the > native case. > > Also add some help text about how KAISER might affect the

[PATCH 24/30] x86, kaiser: disable native VSYSCALL

From: Dave Hansen The VSYSCALL page is mapped by kernel page tables at a kernel address. It is troublesome to support with KAISER in place, so disable the native case. Also add some help text about how KAISER might affect the emulation case as well. Signed-off-by:

[PATCH 24/30] x86, kaiser: disable native VSYSCALL

From: Dave Hansen The VSYSCALL page is mapped by kernel page tables at a kernel address. It is troublesome to support with KAISER in place, so disable the native case. Also add some help text about how KAISER might affect the emulation case as well. Signed-off-by: Dave Hansen Cc: Moritz Lipp