public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31020] New: Use of symlinks in probe process(PATH).* would confuse task finder when matching procname
Date: Wed, 01 Nov 2023 06:26:55 +0000	[thread overview]
Message-ID: <bug-31020-6586@http.sourceware.org/bugzilla/> (raw)

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.

             reply	other threads:[~2023-11-01  6:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01  6:26 agentzh at gmail dot com [this message]
2023-11-04 21:28 ` [Bug runtime/31020] " agentzh at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-31020-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).