On 01/10/2016 09:59 PM, Borislav Petkov wrote: > + Andrey. > > On Fri, Jan 08, 2016 at 03:15:19PM -0800, Andy Lutomirski wrote: >> Otherwise terrible things happen if some of the callbacks end up >> calling into KASAN in unexpected places. >> >> This has no obvious symptoms yet, but adding a memory reference to >> native_flush_tlb_global without this blows up on KASAN kernels. >> >> Signed-off-by: Andy Lutomirski <luto@xxxxxxxxxx> >> --- >> arch/x86/kernel/Makefile | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/arch/x86/kernel/Makefile b/arch/x86/kernel/Makefile >> index b1b78ffe01d0..b7cd5bdf314b 100644 >> --- a/arch/x86/kernel/Makefile >> +++ b/arch/x86/kernel/Makefile >> @@ -19,6 +19,7 @@ endif >> KASAN_SANITIZE_head$(BITS).o := n >> KASAN_SANITIZE_dumpstack.o := n >> KASAN_SANITIZE_dumpstack_$(BITS).o := n >> +KASAN_SANITIZE_paravirt.o := n >> >> CFLAGS_irq.o := -I$(src)/../include/asm/trace > > Shouldn't we take this one irrespectively of what happens to the rest in > the patchset? > I don't think that this patch is the right way to solve the problem. The follow-up patch "x86/kasan: clear kasan_zero_page after TLB flush" should fix Andy's problem. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>