diff options
| author | Josh Poimboeuf | 2020-07-17 09:04:25 -0500 |
|---|---|---|
| committer | Thomas Gleixner | 2020-07-22 23:47:47 +0200 |
| commit | 372a8eaa05998cd45b3417d0e0ffd3a70978211a (patch) | |
| tree | 09a908e123a2665e0804122640bb6c9741309da5 /mm/ptdump.c | |
| parent | de2b41be8fcccb2f5b6c480d35df590476344201 (diff) | |
x86/unwind/orc: Fix ORC for newly forked tasks
The ORC unwinder fails to unwind newly forked tasks which haven't yet
run on the CPU. It correctly reads the 'ret_from_fork' instruction
pointer from the stack, but it incorrectly interprets that value as a
call stack address rather than a "signal" one, so the address gets
incorrectly decremented in the call to orc_find(), resulting in bad ORC
data.
Fix it by forcing 'ret_from_fork' frames to be signal frames.
Reported-by: Wang ShaoBo <bobo.shaobowang@huawei.com>
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Wang ShaoBo <bobo.shaobowang@huawei.com>
Link: https://lkml.kernel.org/r/f91a8778dde8aae7f71884b5df2b16d552040441.1594994374.git.jpoimboe@redhat.com
Diffstat (limited to 'mm/ptdump.c')
0 files changed, 0 insertions, 0 deletions