From: Steve Dickson <SteveD@redhat.com>
To: David Smith <dsmith@redhat.com>
Cc: jiri.horky@gmail.com, Systemtap List <systemtap@sourceware.org>
Subject: Re: [PR15114] What nfsd.* probes does it make sense to add uid/gid variable to?
Date: Thu, 21 Feb 2013 19:05:00 -0000 [thread overview]
Message-ID: <51266FCA.8060905@RedHat.com> (raw)
In-Reply-To: <511AAB96.8030607@redhat.com>
On 12/02/13 15:52, David Smith wrote:
> Steve,
>
> Jiri came up with the idea of adding uid/gid information to the
> nfsd.proc.write aliases. I fleshed out the idea a bit more. For all the
> gory details, see:
>
> <http://sourceware.org/bugzilla/show_bug.cgi?id=15114>
>
> So, we need a couple of questions answered by someone who actually
> understands the NFS daemon. Does it make sense to add uid/gid probe
> variables to read/write and all the remaining nfsd operation probes
> (open lookup commit create unlink rename close)?
I would think so... It seems like its something you could filter on...
> Will that information be available for all the protocol variants (v[2-4])?
They should be... all those ops have do have uids and gids associated
with for permission purposes...
If you need any help testing... just let me know...
steved.
>
> Thanks for the help.
>
prev parent reply other threads:[~2013-02-21 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 20:52 David Smith
2013-02-21 19:05 ` Steve Dickson [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=51266FCA.8060905@RedHat.com \
--to=steved@redhat.com \
--cc=dsmith@redhat.com \
--cc=jiri.horky@gmail.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).