Some times ago I found a race in buffer code - many filesystems do
getblk();mark_buffer_uptodate(); and then write to buffer. If the buffer
is under read i/o, written data are lost.
Andrea certainly submitted me some 2.2.x patches for ext2fs for this that I
merged. I don't know how it
Hi Andrea.
Some times ago I found a race in buffer code - many filesystems do
getblk();mark_buffer_uptodate(); and then write to buffer. If the buffer
is under read i/o, written data are lost.
You created a patch for it, but I don't see it in kernel. What's the
status of this bug? Did anyone
in inode pointer to
directory data, but I'm too lazy to implement it. HPFS is not performance
critical ]
Mikulas Patocka
On Sat, 9 Oct 1999, Andrea Arcangeli wrote:
On Fri, 8 Oct 1999, Mikulas Patocka wrote:
Here goes quick'n'dirty patch. It does bforget(). It should prevent file
corruption.
wrong patch. bforget give you no guarantee at all. bfoget always fallback
to brelse if necessary.
What I said
.
If I'm not mistaken the same scenario applies here just fine.
Here goes quick'n'dirty patch. It does bforget(). It should prevent file
corruption.
Mikulas Patocka
--- linux-2.3.19.tar.gz#utar/linux/fs/ext2/truncate.c Tue Jun 29 18:22:08 1999
+++ linux/fs/ext2/truncate.cFri Oct 8 18:40:36 1999
.
Mikulas Patocka
to do the same (fat currently crashes when writing beyond file
end, other filesystems aren't ported yet)
Mikulas Patocka
On Fri, 5 Nov 1999, Mikulas Patocka wrote:
BTW. neither getblk nor mark_buffer_uptodate check for i/o completion.
That was exactly what I wanted to point out :).
Isn't it race? Many filesystem do it this way.
All depends on the semantics you want I think. It doesn't seems black
