>AFAICS. The next thing I'm going to do is a (dumb) implementation of
>blocking rwlocks. write() being reader and truncate() - writer.
To make the design of the code simpler write(2) should be a writer too.
All the VM checks i_size without any lock. So if you don't want to play
with everything you should grab the writer lock at the VFS layer if you
know your path may change i_size in any way (and write definitely can).
Andrea
-
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/