On Tue, Dec 24, 2013 at 11:58 PM, Masami Hiramatsu <masami.hiramatsu.pt@xxxxxxxxxxx> wrote: > (2013/12/24 18:53), Jovi Zhangwei wrote: >>>> Still no crash, use your kernel config. >>>> memcpy and __memcpy have same address in /proc/kallsyms. >>>> >>>> Looks like a interesting problem. >>> >>> Agreed. In my case, those have same address, but only probing >>> __memcpy caused a kernel crash. I'm not sure why, but it is >>> safe to disable probing on it. >>> >> Shall we need dig further to address the root cause? IMO, the kprobe >> should act same behavior when given same probe address, but it's look >> so weird in your box. :) > > Hmm, right now, I tried it again and found the bug disappeared... > > I'm using the latest tip kernel for the test; > 3ab838d7723e9fbfd49b2d395752bd68e1ef4b71 > > Should I remove this patch until it happens again? > Yes, we can check the problem if it happens again in somewhere. :) Thanks. Jovi. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
