linux-stable.git/scripts/gdb/linux/symbols.py, branch v6.15

scripts/gdb/symbols: determine KASLR offset on s390

2025-03-17T19:17:00+00:00

Use QEMU's qemu.PhyMemMode [1] functionality to read vmcore from the
physical memory the same way the existing dump tooling does this. 
Gracefully handle non-QEMU targets, early boot, and memory corruptions;
print a warning if such situation is detected.

[1] https://qemu-project.gitlab.io/qemu/system/gdb.html#examining-physical-memory

Link: https://lkml.kernel.org/r/20250303110437.79070-1-iii@linux.ibm.com
Signed-off-by: Ilya Leoshkevich 
Acked-by: Jan Kiszka 
Cc: Alexander Gordeev 
Cc: Andrew Donnellan 
Cc: Christian Borntraeger 
Cc: Heiko Carstens 
Cc: Kieran Bingham 
Cc: Nina Schoetterl-Glausch 
Cc: Vasily Gorbik 
Signed-off-by: Andrew Morton

scripts/gdb/linux/symbols.py: address changes to module_sect_attrs

2025-03-17T19:16:59+00:00

When loading symbols from kernel modules we used to iterate
from 0 to module_sect_attrs::nsections, in order to
retrieve their name and address.

However module_sect_attrs::nsections has been removed from
the struct by a previous commit.

Re-arrange the iteration by accessing all items in
module_sect_attrs::grp::bin_attrs[] until NULL is found
(it's a NULL terminated array).

At the same time the symbol address cannot be extracted
from module_sect_attrs::attrs[]::address anymore because
it has also been deleted. Fetch it from
module_sect_attrs::grp::bin_attrs[]::private as described
in 4b2c11e4aaf7.

Link: https://lkml.kernel.org/r/20250221204034.4430-1-antonio@mandelbit.com
Fixes: d8959b947a8d ("module: sysfs: Drop member 'module_sect_attrs::nsections'")
Fixes: 4b2c11e4aaf7 ("module: sysfs: Drop member 'module_sect_attr::address'")
Signed-off-by: Antonio Quartulli 
Reviewed-by: Jan Kiszka 
Cc: Thomas Weißschuh 
Cc: Kieran Bingham 
Signed-off-by: Andrew Morton

gdb: lx-symbols: do not error out on monolithic build

2024-11-15T06:51:14+00:00

This avoids spurious message:
(gdb) lx-symbols
loading vmlinux
No source file named kernel/module/main.c.

Link: https://lkml.kernel.org/r/Zy5ALByQtpO-ddh4@Z926fQmE5jqhFMgp6
Signed-off-by: Etienne Buira 
Cc: Andrew Ballance 
Cc: Kieran Bingham 
Signed-off-by: Andrew Morton

scripts/gdb/symbols: fix invalid escape sequence warning

2024-03-08T00:14:19+00:00

With python 3.12, '\.' results in this warning
    SyntaxWarning: invalid escape sequence '\.'

Link: https://lkml.kernel.org/r/20240304012507.240380-1-andrewjballance@gmail.com
Signed-off-by: Andrew Ballance 
Cc: Jan Kiszka 
Cc: Kieran Bingham 
Cc: Koudai Iwahori 
Cc: Kuan-Ying Lee 
Cc: Luis Chamberlain 
Cc: Pankaj Raghav 
Cc: Shuah Khan 
Signed-off-by: Andrew Morton

revert "scripts/gdb/symbols: add specific ko module load command"

2023-09-19T20:21:33+00:00

Revert 11f956538c07 ("scripts/gdb/symbols: add specific ko module load
command") due to breakage identified by Johannes Berg in [1].

Fixes: 11f956538c07 ("scripts/gdb/symbols: add specific ko module load command")
Reported-by: Johannes Berg 
Closes: https://lkml.kernel.org/r/c44b748307a074d0c250002cdcfe209b8cce93c9.camel@sipsolutions.net [1]
Cc: AngeloGioacchino Del Regno 
Cc: Chinwen Chang 
Cc: Jan Kiszka 
Cc: Kieran Bingham 
Cc: Kuan-Ying Lee 
Cc: Matthias Brugger 
Cc: Qun-Wei Lin 
Signed-off-by: Andrew Morton

scripts/gdb/symbols: add specific ko module load command

2023-08-21T20:46:21+00:00

Patch series "Add GDB memory helper commands", v2.

I've created some GDB commands I think useful when I debug some memory
issues and kernel module issue.

For memory issue, we would like to get slabinfo, slabtrace, page_owner and
vmallocinfo to debug the memory issues.

For module issue, we would like to query kernel module name when we get a
module text address and load module symbol by specific path.

Patch 1-2:
 - Add kernel module related command.
Patch 3-5:
 - Prepares for the memory-related command.
Patch 6-8:
 - Add memory-related commands.


This patch (of 8):

Add lx-symbols  command to support add specific
ko module.

Example output like below:
(gdb) lx-symbols mm/kasan/kasan_test.ko
loading @0xffff800002d30000: mm/kasan/kasan_test.ko

Link: https://lkml.kernel.org/r/20230808083020.22254-1-Kuan-Ying.Lee@mediatek.com
Link: https://lkml.kernel.org/r/20230808083020.22254-2-Kuan-Ying.Lee@mediatek.com
Signed-off-by: Kuan-Ying Lee 
Cc: AngeloGioacchino Del Regno 
Cc: Chinwen Chang 
Cc: Matthias Brugger 
Cc: Qun-Wei Lin 
Signed-off-by: Andrew Morton

scripts/gdb: fix lx-symbols command for arm64 LLVM

2023-08-18T17:18:58+00:00

lx-symbols assumes that module's .text sections is located at
`module->mem[MOD_TEXT].base` and passes it to add-symbol-file command. 
However, .text section follows after .plt section in modules built by LLVM
toolchain for arm64 target.  Symbol addresses are skewed in GDB.

Fix this issue by using the address of .text section stored in
`module->sect_attrs`.

Link: https://lkml.kernel.org/r/20230801121052.2475183-1-koudai@google.com
Signed-off-by: Koudai Iwahori 
Cc: Jan Kiszka 
Cc: Kieran Bingham 
Signed-off-by: Andrew Morton

scripts/gdb: use mem instead of core_layout to get the module address

2023-04-13T21:03:25+00:00

commit ac3b43283923 ("module: replace module_layout with module_memory")
changed the struct module data structure from module_layout to
module_memory. The core_layout member which is used while loading
modules are not available anymore leading to the following error while
running gdb:

(gdb) lx-symbols
loading vmlinux
Python Exception : There is no member named core_layout.
Error occurred in Python: There is no member named core_layout.

Replace core_layout with its new counterpart mem[MOD_TEXT].

Fixes: ac3b43283923 ("module: replace module_layout with module_memory")
Signed-off-by: Pankaj Raghav 
Signed-off-by: Luis Chamberlain

scripts/gdb: Fix gdb 'lx-symbols' command

2022-07-21T17:40:55+00:00

Currently the command 'lx-symbols' in gdb exits with the error`Function
"do_init_module" not defined in "kernel/module.c"`. This occurs because
the file kernel/module.c was moved to kernel/module/main.c.

Fix this breakage by changing the path to "kernel/module/main.c" in
LoadModuleBreakpoint.

Signed-off-by: Khalid Masum 
Acked-by: Luis Chamberlain 
Fixes: cfc1d277891e ("module: Move all into module/")
Reviewed-by: Douglas Anderson 
Signed-off-by: Linus Torvalds

scripts/gdb: handle split debug for vmlinux

2021-11-09T18:02:52+00:00

This is related to two previous changes.  Commit dfe4529ee4d3
("scripts/gdb: find vmlinux where it was before") and commit da036ae14762
("scripts/gdb: handle split debug").

Although Chrome OS has been using the debug suffix for modules for a
while, it has just recently started using it for vmlinux as well.  That
means we've now got to improve the detection of "vmlinux" to also handle
that it might end with ".debug".

Link: https://lkml.kernel.org/r/20211028151120.v2.1.Ie6bd5a232f770acd8c9ffae487a02170bad3e963@changeid
Signed-off-by: Douglas Anderson 
Reviewed-by: Stephen Boyd 
Cc: Jan Kiszka 
Cc: Kieran Bingham 
Cc: Johannes Berg 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds