On Tue, 14 Mar 2000, Matthew Dietrich wrote:
> code. What I would suggest is that someone go through the linux-kernel
> archives for the last few years, search for every time there was a change
> to the VFS, and make sure that the patches code is compliant.
Oh, my... See another posting to the same lists. No need to dig through
the lists - there are very few points where the functions in question are
called (one for each of them) and all tests and locking done by VFS are
there. And tests are pretty explicit. Remove the stuff they cover and
let's look at the rest. If it will be obviously bogus - fine, we found
bugs. If it will turn out to be unneeded - OK, there it goes. If it will
be (for some reason) not enough - again, we found bugs. And yes, there are
filesystems where generic checks are not enough for proper synchronization.
Let's hope that locking provided by VFS is actually OK with your code.
The main reason behind those changes was to simplify the requirements on
interface part of filesystems and make the things we check for as visible
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 15 2000 - 21:00:30 EST