Re: [PATCH 17/19] x86/entry/dumpstack: encode pt_regs pointer in frame pointer

2016-07-21 Thread Andy Lutomirski
On Thu, Jul 21, 2016 at 2:21 PM, Josh Poimboeuf wrote: > With frame pointers, when a task is interrupted, its stack is no longer > completely reliable because the function could have been interrupted > before it had a chance to save the previous frame pointer on the stack. > So the caller of the i

[PATCH 17/19] x86/entry/dumpstack: encode pt_regs pointer in frame pointer

2016-07-21 Thread Josh Poimboeuf
With frame pointers, when a task is interrupted, its stack is no longer completely reliable because the function could have been interrupted before it had a chance to save the previous frame pointer on the stack. So the caller of the interrupted function could get skipped by a stack trace. This is