From: Fawad Lateef <fawadlateef@gmail.com>
To: "ext3crypt@comcast.net" <ext3crypt@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Am I thinking correctly?
Date: Tue, 8 Nov 2005 08:24:17 +0500 [thread overview]
Message-ID: <1e62d1370511071924u4e23c3fdjec82f1713ff8d131@mail.gmail.com> (raw)
In-Reply-To: <110720051724.6127.436F8DDF0006D246000017EF22007348309B9F979D0CCC9B980A@comcast.net>
On 11/7/05, ext3crypt@comcast.net <ext3crypt@comcast.net> wrote:
>
> Kernel Version: 2.6.13
>
> The API will be used, but I am using a simple xor to test with.
>
> The data is getting written to disk, but NOT the buffer I'm sending to submit_bh(). It is writing the buffers from the page I copied???
>
> No messages. I just do the following:
>
> mount the filesystem
> cd to it's root
> cp foo foo2
> sync
> (at this point everything looks fine)
>
> cd ..
> umount the filesystem
> mount the filesystem
> cd to it's root
> cat foo2 (which is now the wrong data)
>
Have you tried your code by writing the data with-out performing any
operation on data (like xor) ? This will tell you whether your
__block_write_full_page is working fine or not because you will get
exactly the same data as of the original file !
And are you also taking care of write operation other than
address_space_operations->writepages ? Because there is also
file_operations->write which ext3 is assgining do_sync_write
(http://sosdg.org/~coywolf/lxr/source/fs/ext3/file.c#L111), so are you
handling this too ?
> I'll attach the code tonight when I have access to it.
>
That will be much better !
And Please Don't do Top-Posting !
--
Fawad Lateef
next prev parent reply other threads:[~2005-11-08 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 17:24 ext3crypt
2005-11-08 3:24 ` Fawad Lateef [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-07 2:18 ext3crypt
2005-11-07 8:54 ` Fawad Lateef
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=1e62d1370511071924u4e23c3fdjec82f1713ff8d131@mail.gmail.com \
--to=fawadlateef@gmail.com \
--cc=ext3crypt@comcast.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®