diff options
| author | Jiri Slaby <jslaby@suse.cz> | 2022-09-06 10:11:23 +0300 |
|---|---|---|
| committer | Borislav Petkov <bp@suse.de> | 2022-09-20 17:11:54 +0300 |
| commit | 5258b80e60da6d8908ae2846b234ed8d9d9d4a19 (patch) | |
| tree | a34b2baea9bf165d3badd3f2cf7cb625b360fc86 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 7987448ffc34f41590bae5b28cd23ca0b8c93291 (diff) | |
| download | linux-5258b80e60da6d8908ae2846b234ed8d9d9d4a19.tar.xz | |
x86/dumpstack: Don't mention RIP in "Code: "
Commit
238c91115cd0 ("x86/dumpstack: Fix misleading instruction pointer error message")
changed the "Code:" line in bug reports when RIP is an invalid pointer.
In particular, the report currently says (for example):
BUG: kernel NULL pointer dereference, address: 0000000000000000
...
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
That
Unable to access opcode bytes at RIP 0xffffffffffffffd6.
is quite confusing as RIP value is 0, not -42. That -42 comes from
"regs->ip - PROLOGUE_SIZE", because Code is dumped with some prologue
(and epilogue).
So do not mention "RIP" on this line in this context.
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lore.kernel.org/r/b772c39f-c5ae-8f17-fe6e-6a2bc4d1f83b@kernel.org
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions