public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: David Smith <dsmith@redhat.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: jiri.horky@gmail.com, Systemtap List <systemtap@sourceware.org>
Subject: [PR15114] What nfsd.* probes does it make sense to add uid/gid variable to?
Date: Tue, 12 Feb 2013 20:52:00 -0000	[thread overview]
Message-ID: <511AAB96.8030607@redhat.com> (raw)

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)? Will that information
be available for all the protocol variants (v[2-4])?

Thanks for the help.

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)

             reply	other threads:[~2013-02-12 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 20:52 David Smith [this message]
2013-02-21 19:05 ` Steve Dickson

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=511AAB96.8030607@redhat.com \
    --to=dsmith@redhat.com \
    --cc=SteveD@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).