From: Fawad Lateef <fawadlateef@gmail.com>
To: Paulo da Silva <psdasilva@esoterica.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Learning ext2 fs
Date: Thu, 27 Oct 2005 23:26:41 +0500 [thread overview]
Message-ID: <1e62d1370510271126i73cd94ebwc66f8d7583fa75c2@mail.gmail.com> (raw)
In-Reply-To: <436116DC.6030104@esoterica.pt>
On 10/27/05, Paulo da Silva <psdasilva@esoterica.pt> wrote:
> I am reading the ext2 fs code. One of my purposes
> is to save the original data of a file to another file
> just before it is changed by write/mmap/whatever.
> Because of mmap (any other reasons?) I thought
> of doing this at "ext2-writepage" or/and
> "ext2-writepages".
>
> Is this the right place?
ya, AFAIK ext2-writepage/s and ext2-readpage/s are the functions
actually dealing with the file data and you can also see
generic_file_write/read assigned to the fields in ext2_file_operations
variable because they also deals with the file data ...
> Is there a lower level where I can read/write blocks
> of data from/to hd instead of full pages?
>
I think at the lower-level you can deal with the block-layer but at
this layer AFAIK you won't be able to distinguish between file data
and file system data/structures because you will be dealing with just
the blocks/chunks of data for block devices.
> How do I tell the really file data from other data?
>
the functions readpage/writepage deals with the file data only not
with the file-system data/structures. Here I am considering by saying
other data you mean file-system data/structures
> I traced these functions but I only got
> "ext2-writepages" to be called. "ext2-writepage"
> was never called using the programs
> I wrote to test this. When is "ext2-writepage" called?
>
I think it doesn't matter that writepage or writepages are called
because both almost do the same thing and the writepages version deals
with more data and in your case the data may be big enough to handle
by the writepages.
> Thanks for any help.
> Any readings advice is also welcome.
>
I think you can first get some detailed understanding of VFS layer and
then you can easily understand the code of the file-system like EXT2 !
--
Fawad Lateef
next prev parent reply other threads:[~2005-10-27 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 18:05 Paulo da Silva
2005-10-27 18:26 ` Fawad Lateef [this message]
2005-10-27 23:38 ` Paulo da Silva
2005-10-28 1:22 ` Fawad Lateef
2005-10-28 19:02 ` Jörn Engel
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=1e62d1370510271126i73cd94ebwc66f8d7583fa75c2@mail.gmail.com \
--to=fawadlateef@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=psdasilva@esoterica.pt \
/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
all inboxes | Powered by JetHome®