Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1638177
| From | "Fogh, Anders" <anders.fogh@gdata-adan.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [kernel-hardening] Re: [RFC, PATCH] x86_64: KAISER - do not mapkernel in user mode |
| Date | 2017-05-09 17:00 +0200 |
| Message-ID | <tFeMi-37Z-9@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <tDG9X-798-11@gated-at.bofh.it> <tECdZ-30b-41@gated-at.bofh.it> <tECdZ-30b-39@gated-at.bofh.it> <tECxm-3oj-69@gated-at.bofh.it> <tECH0-3sL-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
>> i.e. how does it perform on recent AMD systems? Sorry for the latency. Recent AMD is reported by Enrique Nissem to not be vulnerable to the prefetch attack. TSX attack doesn't apply to AMD. Hund, Willems & Holz wrote in 2013 that AMD was vulnerable to that attack. The BTB is almost surely working in a different manner of fashion if at all. So AMD may or may not be vulnerable to the DPF attack, but none of the modern attacks should work - at least out of the box. Best regards, Anders ____________ Virus checked by G Data MailSecurity Version: AVA 25.12310 dated 09.05.2017 Virus news: www.antiviruslab.com
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-04 12:20 +0200
Re: [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-04 14:30 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Thomas Garnier <thgarnie@google.com> - 2017-05-04 17:30 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-05 10:30 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Thomas Garnier <thgarnie@google.com> - 2017-05-05 17:50 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode David Gens <david.gens@cs.tu-darmstadt.de> - 2017-05-06 06:40 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-06 10:40 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Mark Rutland <mark.rutland@arm.com> - 2017-05-08 12:30 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-08 13:00 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Mark Rutland <mark.rutland@arm.com> - 2017-05-08 15:30 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-08 15:50 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-08 16:00 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Thomas Garnier <thgarnie@google.com> - 2017-05-08 16:20 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-08 16:20 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-08 15:30 +0200
Re: [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Christoph Hellwig <hch@infradead.org> - 2017-05-04 17:50 +0200
Re: [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-05 09:50 +0200
Re: [kernel-hardening] Re: [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-07 23:50 +0200
Re: [kernel-hardening] Re: [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Richard Weinberger <richard@nod.at> - 2017-05-08 00:10 +0200
Re: [kernel-hardening] Re: [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-08 00:20 +0200
Re: [kernel-hardening] Re: [RFC, PATCH] x86_64: KAISER - do not mapkernel in user mode "Fogh, Anders" <anders.fogh@gdata-adan.de> - 2017-05-09 17:00 +0200
Re: [kernel-hardening] Re: [RFC, PATCH] x86_64: KAISER - do not mapkernel in user mode Richard Weinberger <richard@nod.at> - 2017-05-09 17:00 +0200
Re: [kernel-hardening] Re: [RFC, PATCH] x86_64: KAISER - do not mapkernel in user mode Rik van Riel <riel@redhat.com> - 2017-05-09 17:40 +0200
Re: [kernel-hardening] Re: [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Richard Weinberger <richard.weinberger@gmail.com> - 2017-05-08 00:10 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Jann Horn <jannh@google.com> - 2017-05-05 18:00 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Daniel Gruss <daniel.gruss@iaik.tugraz.at> - 2017-05-06 10:30 +0200
Re: [kernel-hardening] [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode Jann Horn <jannh@google.com> - 2017-05-05 18:00 +0200
csiph-web