Rob Landley wrote:
You're forgetting the cacheing (dentry and page caches).
We have a writeable filesystem mounted on a read-only block device. This is
an impossible situation we should never have gotten into in the first place.
That's the bug.
For performance reasons, the write stuffs the data into the page cache, and
returns long before the system even attempts to write the data to disk.
(Unless you mount the filesystem O_SYNC, which will kill performance.)
You're right, when I mount the floppy with "-o sync", touch fails
immediately (I did try earlier sync(1), as somebody suggested, and it
didn't matter; yes, I know about the difference between sync(2) and
fsync(2)). On the other hand, umount is supposed to flush all the data
by the time it returns yet still it succeeded.
But overall I agree that we're discussing a situation which should never
happen in the first place, i.e. remount should fail.
Regards,
Evgeny
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]