public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Justin Banks <justinb@bakbone.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Justin Banks <justinb@bakbone.com>, linux-kernel@vger.kernel.org
Subject: Re: Where's the create() pointer?
Date: Sat, 19 Jan 2008 20:31:46 -0700	[thread overview]
Message-ID: <20080120033146.GA6744@bleen.domain.actdsltmp> (raw)
In-Reply-To: <1200773162.9095.11.camel@heimdal.trondhjem.org>

Trond Myklebust wrote
> 
> On Sat, 2008-01-19 at 12:02 -0700, Justin Banks wrote:
> > Trond Myklebust wrote
> > > 
> > > On Sat, 2008-01-19 at 08:07 -0700, Justin Banks wrote:
> > > > It's probably been this way for a long time, and I'm just noticing, but
> > > > I can't seem to find the create() (among others) pointer for NFS filesystems.
> > > > 
> > > > Specifically, If I look at sb->s_root->d_inode->i_op there's no create
> > > > there. How do I find it? I'm guessing that the ability to share mount
> > > > structures between multiple NFS mounts resulted in some kind of fake
> > > > superblock, but I just can't figure out where to find the functions.
> > > 
> > > Why would you want to do this in the first place?
> > 
> > I'm just looking at trapping new creates on NFS, and so I need to find
> > the pointer.
> 
> What is your purpose in trapping creates on the client? Is this for
> accounting purposes? If so, why wouldn't inotify, or even a systemtap
> script suffice?

Could do inotify, except on a large-ish filesystem, it's really
unuseable, if you want to track everything that's going on.

> Anyhow, the simplest way to find the pointer is to grep for nfs_create
> in /proc/kallsyms.

Ugh. That's an ugly way, seems to me. Isn't there a way, given the
superblock? I mean, the VFS does it that way, doesn't it?

-justinb

-- 
Justin Banks
BakBone Software
justinb@bakbone.com

      reply	other threads:[~2008-01-20  3:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19 15:07 Where's the create() pointer? Justin Banks
2008-01-19 16:12 ` Trond Myklebust
2008-01-19 19:02   ` Justin Banks
2008-01-19 20:06     ` Trond Myklebust
2008-01-20  3:31       ` Justin Banks [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=20080120033146.GA6744@bleen.domain.actdsltmp \
    --to=justinb@bakbone.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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