Date: Fri, 28 Jul 2000 02:09:02 -0400 (EDT)
From: Alexander Viro <viro@math.psu.edu>
> Fix further NFS races (Al Viro)
Sounds ominously... All of them?
Well, are there any left that you know about? (Or suspect? :-)
> Audit all char and block drivers to ensure they are safe with the 2.3
> locking - a lot of them are not especially on the open() path.
What about the open() path? They have (or grab) BKL there, so it should
not be something special. Now, read() and write()...
> Stick lock_kernel() calls around driver with issues to hard to fix nicely
> for 2.4 itself
???
Perhaps this is the same as the above item? Alan?
> rw semaphores on inodes to fix read/truncate races ? [Probably fixed]
read/truncate is OK in data part, for metadata rw semaphore looks like a
massive overkill.
Do we still have a problem with the metadata races?
(Yeah, I still have to look at the proposed ext2 patches. They're high
on my priority list.)
> File locking needs checking for races
? Which locking? flock() or VFS one?
Alan? Do you remember which one you were referring to?
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 31 2000 - 21:00:27 EST