Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Report proper module on kernel backtrace
Raghavendra Rao reported that memleak does not display proper name of the related kernel module, but just the "kernel" string, like here for xfs module functions: 131072 bytes in 4 allocations from stack .. bvec_alloc+0x92 [kernel] bio_alloc_bioset+0x13f [kernel] xfs_add_to_ioend+0x2df [kernel] xfs_do_writepage+0x148 [kernel] write_cache_pages+0x171 [kernel] xfs_vm_writepages+0x59 [kernel] do_writepages+0x43 [kernel] ... The kernel resolver code is parsing /proc/kallsyms, which already has the module information in. This patch is adding support to parse the module info from /proc/kallsyms and initialize the module with proper value. Above memleak backtrace now looks like: 131072 bytes in 4 allocations from stack bvec_alloc+0x92 [kernel] bio_alloc_bioset+0x13f [kernel] xfs_add_to_ioend+0x2df [xfs] xfs_do_writepage+0x148 [xfs] write_cache_pages+0x171 [kernel] xfs_vm_writepages+0x59 [xfs] do_writepages+0x43 [kernel] ... Reported-by: Raghavendra Rao <[email protected]> Signed-off-by: Jiri Olsa <[email protected]>
- Loading branch information