(2013/03/19 5:57), Timo Juhani Lindfors wrote: > Masami Hiramatsu <masami.hiramatsu...@hitachi.com> writes: >> Thank you for reporting!! > > Thanks for fixing these! I spent some time trying to automate the > process of finding sensitive functions and eventually resorted into > booting a kvm instance with a minimal initrd to test every single > function in a clean and reproducible environment. > > I found 7 more cases where calling register_kprobe() leads to an instant > kernel panic: > > __flush_tlb_single > native_flush_tlb > native_safe_halt > native_set_pgd > native_set_pmd > native_set_pud > native_write_cr0
Ah, right and Great! these native_* things are too fundamental one. Hmm, curiously, those are defined as inline functions, and I also couldn't find some of those symbols even with your previous kconfig. > You can see full kernel console output for each function at > http://lindi.iki.fi/lindi/linux/kprobes/panics_2013-03-18/ As you can see, your panic messages, most of them caused GFP. This may mean that int3 software exception must not happened on those sites. Not the recursive call. Perhaps, I'd better add those native_* things into symbol-name based blacklist, instead of adding __kprobes, because those are not related to kprobes recursion. Thank you, -- Masami HIRAMATSU IT Management Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu...@hitachi.com -- 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/
