On Fri, 8 Oct 1999, Alexander Viro wrote: >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
- Re: [patch] [possible race in ... Stephen C. Tweedie
- Re: [patch] [possible race in ... Andrea Arcangeli
- Re: [patch] [possible race in ... Benjamin C.R. LaHaise
- Re: how to write get_block? Manfred Spraul
- Re: how to write get_block? Alexander Viro
- Re: how to write get_block? Manfred Spraul
- Re: how to write get_block? Alexander Viro
- Re: how to write get_block? Manfred Spraul
- Re: how to write get_block? Manfred Spraul
- Re: how to write get_block? Alexander Viro
- Re: how to write get_block? Andrea Arcangeli
- Re: how to write get_block? Alexander Viro
- Re: how to write get_block? Andrea Arcangeli
- Re: how to write get_block? Manfred Spraul
- Re: how to write get_block? Manfred Spraul
- Re: how to write get_block? Andrea Arcangeli