On 02/25/2016, 11:00 PM, Jiri Kosina wrote:

quoted

If it was one of the calls _in_ try_to_wake_up() that called to insane 
code, I would have expected to see try_to_wake_up on the stack.

try_to_wake_up() is very likely to be inlined into wake_up_process(), and 
therefore in such cases will never be on the stack as a return address; 
it'll always be wake_up_process().

Actually it is not inlined, see core.s at:
http://labs.suse.cz/jslaby/bug-968218/

thanks,
-- 
js
suse labs