Re: [PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

The kbuild bot found interesting build errors with the new BUILD_BUG_ON on 32bit (64G mem support). I think I went a bit too far with them given the ioremap part is just temporary on early boot. I removed them and tested different configurations trying to use as much fixmap as possible

Re: [PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

The kbuild bot found interesting build errors with the new BUILD_BUG_ON on 32bit (64G mem support). I think I went a bit too far with them given the ioremap part is just temporary on early boot. I removed them and tested different configurations trying to use as much fixmap as possible

Re: [PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

Hi Thomas, [auto build test ERROR on tip/auto-latest] [also build test ERROR on v4.10-rc4 next-20170120] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

Hi Thomas, [auto build test ERROR on tip/auto-latest] [also build test ERROR on v4.10-rc4 next-20170120] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

Hi Thomas, [auto build test ERROR on tip/auto-latest] [also build test ERROR on v4.10-rc4 next-20170120] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

Hi Thomas, [auto build test ERROR on tip/auto-latest] [also build test ERROR on v4.10-rc4 next-20170120] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

On Fri, Jan 20, 2017 at 4:57 PM, Andy Lutomirski wrote: > On Fri, Jan 20, 2017 at 8:41 AM, Thomas Garnier wrote: >> Each processor holds a GDT in its per-cpu structure. The sgdt >> instruction gives the base address of the current GDT. This address can

Re: [PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

On Fri, Jan 20, 2017 at 4:57 PM, Andy Lutomirski wrote: > On Fri, Jan 20, 2017 at 8:41 AM, Thomas Garnier wrote: >> Each processor holds a GDT in its per-cpu structure. The sgdt >> instruction gives the base address of the current GDT. This address can >> be used to bypass KASLR memory

Re: [PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

On Fri, Jan 20, 2017 at 8:41 AM, Thomas Garnier wrote: > Each processor holds a GDT in its per-cpu structure. The sgdt > instruction gives the base address of the current GDT. This address can > be used to bypass KASLR memory randomization. With another bug, an > attacker

Re: [PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

On Fri, Jan 20, 2017 at 8:41 AM, Thomas Garnier wrote: > Each processor holds a GDT in its per-cpu structure. The sgdt > instruction gives the base address of the current GDT. This address can > be used to bypass KASLR memory randomization. With another bug, an > attacker could target other

[PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

Each processor holds a GDT in its per-cpu structure. The sgdt instruction gives the base address of the current GDT. This address can be used to bypass KASLR memory randomization. With another bug, an attacker could target other per-cpu structures or deduce the base of the main memory section

[PATCH v1 2/3] x86: Remap GDT tables in the Fixmap section

Each processor holds a GDT in its per-cpu structure. The sgdt instruction gives the base address of the current GDT. This address can be used to bypass KASLR memory randomization. With another bug, an attacker could target other per-cpu structures or deduce the base of the main memory section