From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org
Cc: paulus@linuxcare.com
Subject: Weird IDE block devices problem
Date: Mon, 13 Dec 1999 10:28:05 +0100 [thread overview]
Message-ID: <19991213102805.001474@mailhost.mipsys.com> (raw)
Hi !
Samuel Rydth (the author of Mac-On-Linux) sent me the following message.
This sound weird since it looks like order is not enforced by the IDE
block driver. Is this normal or is this a kernel bug ? I beleive it
happened with 2.2.10-2.2.13 kernels (I have to confirm this).
On Sun, Dec 12, 1999, Samuel Rydh <samuel@ibrium.se> wrote:
---------------- Begin Forwarded Message ----------------
Btw. I found an oddity with the IDE block device interface
(causes problems with DropStuffit in MacOS 9). In a sequence like
write A to sector N
write B to sector N
read sector N
then the read might not return the information "B" (but something
else). I've always assumed that the block device drivers were
supposed to enforce this consistency but I might be wrong. Everything
work as it should if an extra "fsync" is inserted after each
write. This might impact driver performance though.
----------------- End Forwarded Message -----------------
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~1999-12-13 9:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19991213102805.001474@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com \
/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).