[Bug runtime/31020] New: Use of symlinks in probe process(PATH).* would confuse task finder when matching procname

[Bug runtime/31020] New: Use of symlinks in probe process(PATH).* would confuse task finder when matching procname

[agentzh at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=31020

            Bug ID: 31020
           Summary: Use of symlinks in probe process(PATH).* would confuse
                    task finder when matching procname
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: agentzh at gmail dot com
  Target Milestone: ---

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).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug runtime/31020] Use of symlinks in probe process(PATH).* would confuse task finder when matching procname

[agentzh at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=31020

agentzh <agentzh at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from agentzh <agentzh at gmail dot com> ---
Fixed in commit 81b2ee28207.

-- 
You are receiving this mail because:
You are the assignee for the bug.