Re: Linux 4.15-rc7

On Thu 2018-01-11 15:07:22, Jiri Kosina wrote: > On Thu, 11 Jan 2018, Pavel Machek wrote: > > > Is anyone working on KPTI for x86-32? SLES11 should still be supported, > > and that should have x86-32 version; any chance SUSE can share some > > patches? > > We are sharing sources of all our

Re: Linux 4.15-rc7

On Thu 2018-01-11 15:07:22, Jiri Kosina wrote: > On Thu, 11 Jan 2018, Pavel Machek wrote: > > > Is anyone working on KPTI for x86-32? SLES11 should still be supported, > > and that should have x86-32 version; any chance SUSE can share some > > patches? > > We are sharing sources of all our

kernel page table isolation for x86-32 was Re: Linux 4.15-rc7

Hi! > > I'll try to do the right thing. OTOH... I don't like the fact that > > kernel memory on my machine is currently readable, probably even from > > javascript. > > Oh, absolutely. I'm just saying that it's probably best to try to > start from the x86-64 KPTI model, and see how that works

kernel page table isolation for x86-32 was Re: Linux 4.15-rc7

Hi! > > I'll try to do the right thing. OTOH... I don't like the fact that > > kernel memory on my machine is currently readable, probably even from > > javascript. > > Oh, absolutely. I'm just saying that it's probably best to try to > start from the x86-64 KPTI model, and see how that works

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 11:08:58PM +0100, Arnd Bergmann wrote: > On Fri, Jan 12, 2018 at 11:04 PM, wrote: > > On Fri, Jan 12, 2018 at 09:11:38PM +0100, Arnd Bergmann wrote: > > > >> - I haven't found a definite answer on whether Netburst-based CPUs > >> are affected by

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 11:08:58PM +0100, Arnd Bergmann wrote: > On Fri, Jan 12, 2018 at 11:04 PM, wrote: > > On Fri, Jan 12, 2018 at 09:11:38PM +0100, Arnd Bergmann wrote: > > > >> - I haven't found a definite answer on whether Netburst-based CPUs > >> are affected by meltdown at all. Some

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 11:04 PM, wrote: > On Fri, Jan 12, 2018 at 09:11:38PM +0100, Arnd Bergmann wrote: > >> - I haven't found a definite answer on whether Netburst-based CPUs >> are affected by meltdown at all. Some people claim it's affected, >> others say it's not.

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 11:04 PM, wrote: > On Fri, Jan 12, 2018 at 09:11:38PM +0100, Arnd Bergmann wrote: > >> - I haven't found a definite answer on whether Netburst-based CPUs >> are affected by meltdown at all. Some people claim it's affected, >> others say it's not. If the code from

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 09:11:38PM +0100, Arnd Bergmann wrote: > On Fri, Jan 12, 2018 at 6:20 PM, wrote: > > On Fri, Jan 12, 2018 at 02:23:20PM +0100, Arnd Bergmann wrote: > > >> Could you be more specific which 32-bit x86 chips you have that are > >> affected by Meltdown?

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 09:11:38PM +0100, Arnd Bergmann wrote: > On Fri, Jan 12, 2018 at 6:20 PM, wrote: > > On Fri, Jan 12, 2018 at 02:23:20PM +0100, Arnd Bergmann wrote: > > >> Could you be more specific which 32-bit x86 chips you have that are > >> affected by Meltdown? Do you mean pre-2004

Re: Linux 4.15-rc7

On Fri 2018-01-12 11:44:48, Linus Torvalds wrote: > On Fri, Jan 12, 2018 at 11:38 AM, Pavel Machek wrote: > > > > I'll try to do the right thing. OTOH... I don't like the fact that > > kernel memory on my machine is currently readable, probably even from > > javascript. > > Oh,

Re: Linux 4.15-rc7

On Fri 2018-01-12 11:44:48, Linus Torvalds wrote: > On Fri, Jan 12, 2018 at 11:38 AM, Pavel Machek wrote: > > > > I'll try to do the right thing. OTOH... I don't like the fact that > > kernel memory on my machine is currently readable, probably even from > > javascript. > > Oh, absolutely. I'm

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 6:20 PM, wrote: > On Fri, Jan 12, 2018 at 02:23:20PM +0100, Arnd Bergmann wrote: >> Could you be more specific which 32-bit x86 chips you have that are >> affected by Meltdown? Do you mean pre-2004 Pentiums or Core-Duo >> laptops? I would guess that

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 6:20 PM, wrote: > On Fri, Jan 12, 2018 at 02:23:20PM +0100, Arnd Bergmann wrote: >> Could you be more specific which 32-bit x86 chips you have that are >> affected by Meltdown? Do you mean pre-2004 Pentiums or Core-Duo >> laptops? I would guess that Cyrix/Natsemi/AMD

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 11:38 AM, Pavel Machek wrote: > > I'll try to do the right thing. OTOH... I don't like the fact that > kernel memory on my machine is currently readable, probably even from > javascript. Oh, absolutely. I'm just saying that it's probably best to try to start

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 11:38 AM, Pavel Machek wrote: > > I'll try to do the right thing. OTOH... I don't like the fact that > kernel memory on my machine is currently readable, probably even from > javascript. Oh, absolutely. I'm just saying that it's probably best to try to start from the

Re: Linux 4.15-rc7

On Fri 2018-01-12 09:34:03, Linus Torvalds wrote: > On Fri, Jan 12, 2018 at 5:23 AM, Arnd Bergmann wrote: > > > > However, there is an important difference between KPTI and X86_4G: > > The former unmaps the kernel pages from the user space page tables, > > but keeps both the linear

Re: Linux 4.15-rc7

On Fri 2018-01-12 09:34:03, Linus Torvalds wrote: > On Fri, Jan 12, 2018 at 5:23 AM, Arnd Bergmann wrote: > > > > However, there is an important difference between KPTI and X86_4G: > > The former unmaps the kernel pages from the user space page tables, > > but keeps both the linear mapping and

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 5:23 AM, Arnd Bergmann wrote: > > However, there is an important difference between KPTI and X86_4G: > The former unmaps the kernel pages from the user space page tables, > but keeps both the linear mapping and the user pages visible in > kernel mode, while

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 5:23 AM, Arnd Bergmann wrote: > > However, there is an important difference between KPTI and X86_4G: > The former unmaps the kernel pages from the user space page tables, > but keeps both the linear mapping and the user pages visible in > kernel mode, while the latter must

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 02:23:20PM +0100, Arnd Bergmann wrote: > On Fri, Jan 12, 2018 at 12:06 PM, Pavel Machek wrote: > > Hi! > > > >> Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? > > > > Good point. Is that still supported? Was it ever? > > > > Umm. I seem

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 02:23:20PM +0100, Arnd Bergmann wrote: > On Fri, Jan 12, 2018 at 12:06 PM, Pavel Machek wrote: > > Hi! > > > >> Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? > > > > Good point. Is that still supported? Was it ever? > > > > Umm. I seem to recall that

Re: Linux 4.15-rc7

Hi! > >> Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? > > > > Good point. Is that still supported? Was it ever? > > > > Umm. I seem to recall that 4G/4G layout was out of tree but never > > merged. > > I think that's correct: it was in RHEL3 and RHEL4 but never merged >

Re: Linux 4.15-rc7

Hi! > >> Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? > > > > Good point. Is that still supported? Was it ever? > > > > Umm. I seem to recall that 4G/4G layout was out of tree but never > > merged. > > I think that's correct: it was in RHEL3 and RHEL4 but never merged >

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 12:06 PM, Pavel Machek wrote: > Hi! > >> Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? > > Good point. Is that still supported? Was it ever? > > Umm. I seem to recall that 4G/4G layout was out of tree but never > merged. I think that's

Re: Linux 4.15-rc7

On Fri, Jan 12, 2018 at 12:06 PM, Pavel Machek wrote: > Hi! > >> Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? > > Good point. Is that still supported? Was it ever? > > Umm. I seem to recall that 4G/4G layout was out of tree but never > merged. I think that's correct: it

Re: Linux 4.15-rc7

Hi! > Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? Good point. Is that still supported? Was it ever? Umm. I seem to recall that 4G/4G layout was out of tree but never merged. High Memory Support 1. off (NOHIGHMEM) 2. 4GB (HIGHMEM4G) > 3. 64GB (HIGHMEM64G)

Re: Linux 4.15-rc7

Hi! > Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? Good point. Is that still supported? Was it ever? Umm. I seem to recall that 4G/4G layout was out of tree but never merged. High Memory Support 1. off (NOHIGHMEM) 2. 4GB (HIGHMEM4G) > 3. 64GB (HIGHMEM64G)

Re: Linux 4.15-rc7

On Thu, 11 Jan 2018, Pavel Machek wrote: > Is anyone working on KPTI for x86-32? SLES11 should still be supported, > and that should have x86-32 version; any chance SUSE can share some > patches? We are sharing sources of all our kernels at http://kernel.suse.com/ If you can find the

Re: Linux 4.15-rc7

On Thu, 11 Jan 2018, Pavel Machek wrote: > Is anyone working on KPTI for x86-32? SLES11 should still be supported, > and that should have x86-32 version; any chance SUSE can share some > patches? We are sharing sources of all our kernels at http://kernel.suse.com/ If you can find the

Re: Linux 4.15-rc7

On 11.01.2018 13:29, Olivier Galibert wrote: > Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? 4g/4g was never accepted upstream > > OG. > > > On Thu, Jan 11, 2018 at 12:32 AM, Pavel Machek wrote: >> Hi! >> >>> The one thing I want to do now that

Re: Linux 4.15-rc7

On 11.01.2018 13:29, Olivier Galibert wrote: > Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? 4g/4g was never accepted upstream > > OG. > > > On Thu, Jan 11, 2018 at 12:32 AM, Pavel Machek wrote: >> Hi! >> >>> The one thing I want to do now that Meltdown and Spectre

Re: Linux 4.15-rc7

Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? OG. On Thu, Jan 11, 2018 at 12:32 AM, Pavel Machek wrote: > Hi! > >> The one thing I want to do now that Meltdown and Spectre are public, >> is to give a *big* shout-out to the x86 people, and Thomas Gleixner

Re: Linux 4.15-rc7

Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI? OG. On Thu, Jan 11, 2018 at 12:32 AM, Pavel Machek wrote: > Hi! > >> The one thing I want to do now that Meltdown and Spectre are public, >> is to give a *big* shout-out to the x86 people, and Thomas Gleixner in >>

Re: Linux 4.15-rc7

Hi! > The one thing I want to do now that Meltdown and Spectre are public, > is to give a *big* shout-out to the x86 people, and Thomas Gleixner in > particular for really being on top of this. It's been one huge > annoyance, and honestly, Thomas really went over and beyond in this > whole mess.

Re: Linux 4.15-rc7

Hi! > The one thing I want to do now that Meltdown and Spectre are public, > is to give a *big* shout-out to the x86 people, and Thomas Gleixner in > particular for really being on top of this. It's been one huge > annoyance, and honestly, Thomas really went over and beyond in this > whole mess.

Re: Linux 4.15-rc7

Linus, On Sun, 7 Jan 2018, Linus Torvalds wrote: > The one thing I want to do now that Meltdown and Spectre are public, > is to give a *big* shout-out to the x86 people, and Thomas Gleixner in > particular for really being on top of this. It's been one huge > annoyance, and honestly, Thomas

Re: Linux 4.15-rc7

Linus, On Sun, 7 Jan 2018, Linus Torvalds wrote: > The one thing I want to do now that Meltdown and Spectre are public, > is to give a *big* shout-out to the x86 people, and Thomas Gleixner in > particular for really being on top of this. It's been one huge > annoyance, and honestly, Thomas

Linux 4.15-rc7

mpstack: Fix partial register dumps x86/dumpstack: Print registers for first stack frame Kees Cook (1): exec: Weaken dumpability for secureexec Klaus Goger (1): arm64: dts: rockchip: remove vdd_log from rk3399-puma Linus Torvalds (1): Linux 4.15-rc7 Lucas De Marchi (1):

Linux 4.15-rc7

mpstack: Fix partial register dumps x86/dumpstack: Print registers for first stack frame Kees Cook (1): exec: Weaken dumpability for secureexec Klaus Goger (1): arm64: dts: rockchip: remove vdd_log from rk3399-puma Linus Torvalds (1): Linux 4.15-rc7 Lucas De Marchi (1):

[GIT PULL] KVM fixes for Linux 4.15-rc7

Linus, The following changes since commit aa12f594f97efe50223611dbd13ecca4e8dafee6: tools/kvm_stat: sort '-f help' output (2017-12-21 13:03:32 +0100) are available in the Git repository at: git://git.kernel.org/pub/scm/virt/kvm/kvm for-linus for you to fetch changes up to

[GIT PULL] KVM fixes for Linux 4.15-rc7

Linus, The following changes since commit aa12f594f97efe50223611dbd13ecca4e8dafee6: tools/kvm_stat: sort '-f help' output (2017-12-21 13:03:32 +0100) are available in the Git repository at: git://git.kernel.org/pub/scm/virt/kvm/kvm for-linus for you to fetch changes up to