* Ingo Molnar wrote:
> > was supposed to be a synchronization point, but if you do
> >
> > git diff 9a818d1a3235..9a818d1a3235^
> >
> > it isn't actually synchronized. It's *almost* synchronized, but not
> > quite. How did those cherry-picks that were already upstream
* Ingo Molnar wrote:
> > was supposed to be a synchronization point, but if you do
> >
> > git diff 9a818d1a3235..9a818d1a3235^
> >
> > it isn't actually synchronized. It's *almost* synchronized, but not
> > quite. How did those cherry-picks that were already upstream end up
> > causing
* Linus Torvalds wrote:
> On Fri, Dec 15, 2017 at 5:58 PM, Ingo Molnar wrote:
> >
> > These are the x86-64 low level entry code preparatory patches for the page
> > table
> > isolation patches - which are required for PTI, which addresses KASLR
* Linus Torvalds wrote:
> On Fri, Dec 15, 2017 at 5:58 PM, Ingo Molnar wrote:
> >
> > These are the x86-64 low level entry code preparatory patches for the page
> > table
> > isolation patches - which are required for PTI, which addresses KASLR and
> > similar
> > information leaks.
>
>
On Fri, Dec 15, 2017 at 5:58 PM, Ingo Molnar wrote:
>
> These are the x86-64 low level entry code preparatory patches for the page
> table
> isolation patches - which are required for PTI, which addresses KASLR and
> similar
> information leaks.
Ugh.
Ok, I've read through
On Fri, Dec 15, 2017 at 5:58 PM, Ingo Molnar wrote:
>
> These are the x86-64 low level entry code preparatory patches for the page
> table
> isolation patches - which are required for PTI, which addresses KASLR and
> similar
> information leaks.
Ugh.
Ok, I've read through this, and while I
6 matches
Mail list logo