From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: given fs dies if SMP, if PREEMPT, if open two or more
Date: 23 Oct 2003 16:17:44 -0600 [thread overview]
Message-ID: <1066947463.13459.5.camel@patehci2> (raw)
You may have noticed, I recently arrived here in linux-fsdevel,
committed to trying to help make linux udf.ko ever more perfect.
Can anyone here advise me specifically what to try next?
So far we've demoed some trouble in the linux-fsdevel thread "zeroes
read back more often than appended". That trouble occurs if CONFIG_SMP,
if CONFIG_PREEMPT, or if I append nonzero bytes to multiple files in a
round robin sequence.
That says to me something in udf.ko doesn't know how to reenter itself,
right? So my next step is to try reading while writing, to see if that
breaks also, right? No?
What do you think?
Once my random guesses of specific kinds of trivial stress cease to
cause trouble, I figure I will then try the more complex:
http://www.codemonkey.org.uk/cruft/
http://www.zip.com.au/~akpm/linux/patches/stuff/
http://ltp.sourceforge.net/
http://www.iozone.org
http://www.google.com/search?q=postmark+linux
http://www.connectathon.org/
http://www.google.com/search?q=bonnie+linux
I mean to be asking what do you think I should try before risking the
possibly less discovered troubles per hour of that alternative.
What do you think?
Pat LaVarre
next reply other threads:[~2003-10-23 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 22:17 Pat LaVarre [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-25 17:06 given fs dies if SMP, if PREEMPT, if open two or more 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=1066947463.13459.5.camel@patehci2 \
--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