public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/15114] [PATCH] Propagate uid and gid from nfsd module as well
Date: Thu, 07 Feb 2013 21:33:00 -0000	[thread overview]
Message-ID: <bug-15114-6586-c7o82hByGI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15114-6586@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15114

--- Comment #4 from David Smith <dsmith at redhat dot com> 2013-02-07 21:32:27 UTC ---
Created attachment 6855
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6855
uid/gid patch for read/write

Here's a patch that adds uid/gid to nfsd.proc*.read and nfsd.proc*.write (and
adds a compile-time test). I was aided by the fact that the code was exactly
the same for all protocol variants.

The only other remaining question here is what other nfs operations does it
make sense to do this for? open? lookup? commit? create? unlink? rename? close?

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2013-02-07 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07  8:36 [Bug tapsets/15114] New: " jiri.horky at gmail dot com
2013-02-07 16:08 ` [Bug tapsets/15114] " dsmith at redhat dot com
2013-02-07 20:12 ` fche at redhat dot com
2013-02-07 20:31 ` jiri.horky at gmail dot com
2013-02-07 21:33 ` dsmith at redhat dot com [this message]
2013-03-25 19:57 ` dsmith at redhat dot com

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-15114-6586-c7o82hByGI@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).