On Thu, Jul 10, 2014 at 11:44:43PM +0200, Jiri Kosina wrote: > On Thu, 10 Jul 2014, Josh Poimboeuf wrote: > > > I did some testing with kpatch and I found one minor issue. The dynamically > > allocated trampoline seems to confuse dump_stack() somewhat. > > > > I added a dump_stack() call in my ftrace_ops callback function > > (kpatch_ftrace_handler) which had a filter on meminfo_proc_show(). > > Interesting. Are you using dwarf2 unwinder for stack dumping by any > chance?
I think so (but not sure). How can I check? I do see the following macros being defined in my kernel build: -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 > It seems to get things right here. Will look into it more tomorrow. Thanks, please let me know what you find... -- Josh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
