From: "m.j.harvey at imperial dot ac.uk" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/26666] nfsd tapset - fh_export and fh_dentry always NULL for NFSv3
Date: Fri, 25 Sep 2020 23:06:57 +0000 [thread overview]
Message-ID: <bug-26666-6586-HSxhaDEjYX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26666-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26666
--- Comment #1 from MJH <m.j.harvey at imperial dot ac.uk> ---
It's not a systemtap bug, per se. The examples will never have worked with
nfsv3.
To get the filename of an access, trap the return of nfds.fh_verify, eg
probe module("nfsd").function("fh_verify").return {
printf("%s\n", inode_path( $fhp->fh_dentry->d_inode ) )
}
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-09-25 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 18:03 [Bug tapsets/26666] New: " m.j.harvey at imperial dot ac.uk
2020-09-25 23:06 ` m.j.harvey at imperial dot ac.uk [this message]
2020-09-25 23:36 ` [Bug tapsets/26666] " fche at redhat dot com
2020-09-29 17:12 ` m.j.harvey at imperial dot ac.uk
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-26666-6586-HSxhaDEjYX@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).