From: "Siddhartha Jain" <sid@netmagicsolutions.com>
To: "Linux fs-devel" <linux-fsdevel@vger.kernel.org>
Subject: RE: Write calls
Date: Wed, 23 Jun 2004 21:00:55 +0530 [thread overview]
Message-ID: <002d01c45937$13404930$a101010a@nsplsales> (raw)
In-Reply-To: <1088003447.18627.2678.camel@hades.cambridge.redhat.com>
>
>On Wed, 2004-06-23 at 17:05 +0530, Siddhartha Jain wrote:
>> Basically, I want to find out the all kernel functions thru which every
>> write call (not FS dependant) passes.
>
>mmap?
>
>
I am sorry. To put it differently, if I wanted to *snoop* on all bytes
written to all/any files on the system, irrespective of the FS, what
functions would I need to modify in the kernel? The objective is to be able
to replicate directories.
Thanks,
Siddhartha
next prev parent reply other threads:[~2004-06-23 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 11:35 Write calls Siddhartha Jain
2004-06-23 15:10 ` David Woodhouse
2004-06-23 15:30 ` Siddhartha Jain [this message]
2004-06-23 16:47 ` Jamie Lokier
2004-06-24 9:10 ` Siddhartha Jain
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='002d01c45937$13404930$a101010a@nsplsales' \
--to=sid@netmagicsolutions.com \
--cc=linux-fsdevel@vger.kernel.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 NNTP newsgroup(s).