On Fri, Jul 17, 2015 at 11:47:28AM -0500, Josh Poimboeuf wrote: > stackvalidate reports the following warnings for __schedule(): > > stackvalidate: kernel/sched/core.o: __schedule()+0x3e7: duplicate frame pointer save > stackvalidate: kernel/sched/core.o: __schedule()+0x424: sibling call from callable instruction with changed frame pointer > stackvalidate: kernel/sched/core.o: __schedule()+0x431: call without frame pointer save/setup > stackvalidate: kernel/sched/core.o: __schedule()+0x8b8: frame pointer state mismatch > stackvalidate: kernel/sched/core.o: __schedule()+0x447: frame pointer state mismatch > > __schedule() is obviously a special case which is allowed to do unusual > things with the frame pointer. Yes, but is the code actually correct? We can't dismiss the warnings just on that basis alone. -- To unsubscribe from this list: send the line "unsubscribe live-patching" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
