Re: [PATCH v7 02/12] x86_64: load_percpu_segment: read irq_stack_union.gs_base before load_segment

2014-11-25 Thread Dmitry Chernenkov
LGTM On Mon, Nov 24, 2014 at 9:02 PM, Andrey Ryabinin wrote: > Reading irq_stack_union.gs_base after load_segment creates troubles for kasan. > Compiler inserts __asan_load in between load_segment and wrmsrl. If kernel > built with stackprotector this will result in boot failure because

Re: [PATCH v7 02/12] x86_64: load_percpu_segment: read irq_stack_union.gs_base before load_segment

2014-11-25 Thread Dmitry Chernenkov
LGTM On Mon, Nov 24, 2014 at 9:02 PM, Andrey Ryabinin a.ryabi...@samsung.com wrote: Reading irq_stack_union.gs_base after load_segment creates troubles for kasan. Compiler inserts __asan_load in between load_segment and wrmsrl. If kernel built with stackprotector this will result in boot

[PATCH v7 02/12] x86_64: load_percpu_segment: read irq_stack_union.gs_base before load_segment

2014-11-24 Thread Andrey Ryabinin
Reading irq_stack_union.gs_base after load_segment creates troubles for kasan. Compiler inserts __asan_load in between load_segment and wrmsrl. If kernel built with stackprotector this will result in boot failure because __asan_load has stackprotector. To avoid this irq_stack_union.gs_base stored

[PATCH v7 02/12] x86_64: load_percpu_segment: read irq_stack_union.gs_base before load_segment

2014-11-24 Thread Andrey Ryabinin
Reading irq_stack_union.gs_base after load_segment creates troubles for kasan. Compiler inserts __asan_load in between load_segment and wrmsrl. If kernel built with stackprotector this will result in boot failure because __asan_load has stackprotector. To avoid this irq_stack_union.gs_base stored