On 11/18/2014 07:09 PM, Andrey Ryabinin wrote: > Yes with CONFIG_KASAN_INLINE you will get GPF instead of kasan report. > For userspaces addresses we don't have shadow memory. In outline case > I just check address itself before checking shadow. In inline case compiler > just checks shadow, so there is no way to avoid GPF. > > To be able to print report instead of GPF, I need to treat GPFs in a special > way if inline instrumentation was enabled, but it's not done yet.
I went ahead and tested it with the test module, which worked perfectly. No more complaints here... >> > I remembered that one of the biggest changes in kasan was the introduction >> > of >> > inline instrumentation, so I went ahead to disable it and see if it helps. >> > But >> > the only result of that was having the boot process hang pretty early: >> > >> > [...] >> > [ 0.000000] IOAPIC[0]: apic_id 21, version 17, address 0xfec00000, GSI >> > 0-23 >> > [ 0.000000] Processors: 20 >> > [ 0.000000] smpboot: Allowing 24 CPUs, 4 hotplug CPUs >> > [ 0.000000] e820: [mem 0xd0000000-0xffffffff] available for PCI devices >> > [ 0.000000] Booting paravirtualized kernel on KVM >> > [ 0.000000] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:24 nr_cpu_ids:24 >> > nr_node_ids:1 >> > [ 0.000000] PERCPU: Embedded 491 pages/cpu @ffff8808dce00000 s1971864 >> > r8192 d31080 u2097152 >> > *HANG* >> > > This hang happens only with your error patch above or even without it? It happens even without the patch. Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
