On Mon, 24 Jul 2000, Alexander Viro wrote:
> Not needed. That race is taken care of - readpage() never does access past
> i_size and has the page locked, while vmtruncate() starts with setting
> i_size (on shrinking truncate(), that is), then goes through all pages in
> affected area and grabs the lock on all of them (one by one, not
> simultaneously, indeed) and only then calls ->truncate().
That assumes that i_size is atomically updated, which currently is not the
case on 32 bit platforms.
-ben
