public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Daire Byrne <daire@dneg.com>
To: systemtap@sourceware.org
Subject: newer kernel+systemtap & nfs.fop.open
Date: Thu, 10 Mar 2022 19:58:39 +0000	[thread overview]
Message-ID: <CAPt2mGNkfGtz0JOJkm0d1kQ5QTwj+nqif-Q1AJp=fw-yKV1_bA@mail.gmail.com> (raw)

Hi,

Bit of a newbie question, but I'm trying to port some older code to a
newer version of systemtap (4.7pre) and I'm seeing a change in
behaviour in the output of this:

stap -e 'probe nfs.fop.open { filename = sprintf("%s",
d_path(&$filp->f_path)); printf("filename: %s\n", filename)}'

On previous versions (RHEL7, stap v4.1), the resulting filename had
the full path including the mounted directory path or autompunt path,
But on newer version of the kernel and systemtap, it seems like only
the file path after the NFS mountpoint is being printed.

Is there some other trick now required with the
d_path((&$filp->f_path)) to include the NFS mountpoint location and
provide the full path?

Many thanks,

Daire

             reply	other threads:[~2022-03-10 19:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 19:58 Daire Byrne [this message]
2022-04-01 12:26 ` Daire Byrne
2022-04-01 14:05   ` David Smith
2022-04-01 14:55   ` Serhei Makarov
2022-04-01 20:13     ` Serhei Makarov
2022-04-04 11:21       ` Daire Byrne
2022-04-04 12:28         ` Daire Byrne

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='CAPt2mGNkfGtz0JOJkm0d1kQ5QTwj+nqif-Q1AJp=fw-yKV1_bA@mail.gmail.com' \
    --to=daire@dneg.com \
    --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).