diff options
| author | Josh Poimboeuf <jpoimboe@redhat.com> | 2020-07-17 17:04:25 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-08-05 10:59:51 +0300 |
| commit | 32344d2993b0228e238dff163d7447dcf250f147 (patch) | |
| tree | a599f1efa9c1da045a131aefc906652b89e8c279 /scripts/gdb/linux/utils.py | |
| parent | a14d6a9ddf33c13bb58cda5fb0ad8edae628b9f8 (diff) | |
| download | linux-32344d2993b0228e238dff163d7447dcf250f147.tar.xz | |
x86/unwind/orc: Fix ORC for newly forked tasks
[ Upstream commit 372a8eaa05998cd45b3417d0e0ffd3a70978211a ]
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
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions