On Sat, Sep 20, 2008 at 05:25:22AM +0200, Jan Kara wrote: > Reading i_size is a different matter - see > i_size_read function. We use seqlock for that - essentially we use an > atomic counter which is incremented on every change of i_size and check > that it's value before we started reading i_size and after we have > finished reading it has not changed. I hope this helps. Just to clarify for Shin Hong's benefit: this is necessary only on SMP (or CONFIG_PREEMPT) 32-bit platforms in order to make sure we read a coherent 64-bit i_size value. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
