Bug 31020 - Use of symlinks in probe process(PATH).* would confuse task finder when matching procname
Summary: Use of symlinks in probe process(PATH).* would confuse task finder when match...
Status: RESOLVED FIXED
Alias: None
Product: systemtap
Classification: Unclassified
Component: runtime (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-01 06:26 UTC by agentzh
Modified: 2023-11-04 21:28 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description agentzh 2023-11-01 06:26:55 UTC
For probes like `process("PATH").begin` and `process("PATH").function`, when we use symlinks for PATH, the task finder would silently fail to match the target processes' procname.

We should always resolve PATH at runtime to the real file path. The target processes' process names and mmap file paths are always real file paths.

This is especially important once we do early inode uprobe registrations right before the task finder is started, where we also resolve the real inode for the PATH string without inspecting running processes (and also when we have to specify symlinks like /proc/PID/exe link for deleted ELF files).
Comment 1 agentzh 2023-11-04 21:28:48 UTC
Fixed in commit 81b2ee28207.