From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: vfs whitebox test
Date: 24 Nov 2003 16:29:22 -0700 [thread overview]
Message-ID: <1069716562.4649.14.camel@patrh9> (raw)
Anybody already pull together some more closely interactive way of
trying creative patterns of calls thru the vfs layer?
I ask because I'm still hung up on my demo that udf.ko can't reliably
write more than one file at a time:
http://marc.theaimsgroup.com/?l=linux-fsdevel&m=106676214111422
List: linux-fsdevel
Subject: Re: zeroes read back more often than appended
Date: 2003-10-21 18:44:54
I'm guessing what makes that demo tough to analyse is that I wrote it up
at the high level of fopen/ fwrite/ fclose/ hexdump. I'm guessing
translating that demo down to the more verbose level of open/ write/
read/ close actually won't make the demo significantly easier to
analyse. I'm thinking I have to drop down to the vfs level.
Can I somehow drop down to the vfs level?
Maybe I could run the fs as a .so?
Can I help in any way quicker than deciphering the source of udf.ko?
Pat LaVarre
next reply other threads:[~2003-11-24 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 23:29 Pat LaVarre [this message]
2003-11-25 15:46 ` vfs whitebox test Pat LaVarre
2003-11-25 17:04 ` Pat LaVarre
2003-11-25 17:06 ` Randy.Dunlap
2003-11-25 17:12 ` Pat LaVarre
2003-11-25 19:59 ` Pat LaVarre
2003-11-25 17:09 ` Randy.Dunlap
2003-11-25 17:33 ` Pat LaVarre
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 19:14 Pat LaVarre
2003-12-05 18:12 ` Pat LaVarre
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=1069716562.4649.14.camel@patrh9 \
--to=p.lavarre@ieee.org \
--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