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: Tue, 29 Sep 2020 17:12:39 +0000 [thread overview]
Message-ID: <bug-26666-6586-3Diq3WgS2a@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 #3 from MJH <m.j.harvey at imperial dot ac.uk> ---
(In reply to Frank Ch. Eigler from comment #2)
> Do you think we should extend the example, or make a nfsd3_watch.stp sample?
I'd be inclined to make a separate one, maybe renaming the others nfs4*.
The probe I peosted earlier relied on a return probe being able to access final
values of an argument. This worked on my test machine but not in our production
environment, and I understand the former is not intended behaviour. So, here's
what we are using now:
global ip
global pf
global uid
probe module("nfsd").function("nfsd3_proc_*") {
ip[tid()] = addr_from_rqst_str($rqstp)
pf[tid()] = probefunc()
uid[tid()] = $rqstp->rq_cred->cr_uid->val
}
probe module("nfsd").function("nfsd_permission") {
printf("%d %s %s : %s\n", uid[tid()], pf[tid()], ip[tid()], inode_path(
$dentry->d_inode ) )
}
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2020-09-29 17:12 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 ` [Bug tapsets/26666] " m.j.harvey at imperial dot ac.uk
2020-09-25 23:36 ` fche at redhat dot com
2020-09-29 17:12 ` m.j.harvey at imperial dot ac.uk [this message]
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-3Diq3WgS2a@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).