On Tue, Sep 08, 2009 at 01:41:03PM +0200, Jan Kara wrote: > In theory it could happen that on one CPU we initialize a new inode but clearing > of I_NEW | I_LOCK gets reordered before some of the initialization. Thus on > another CPU we return not fully uptodate inode from iget_locked(). > > This seems to fix a corruption issue on ext3 mounted over NFS. > > Signed-off-by: Jan Kara <jack@xxxxxxx> Looks good to me. Impressive that this causes real life issues. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
