Messages in this thread | | | Date | Sat, 12 Sep 2009 16:06:25 +0100 | From | Al Viro <> | Subject | Re: [PATCH] fs: Make sure data stored into inode is properly seen before unlocking new inode |
| |
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.
Nice catch. ACK.
> Since Al doesn't seem to be online, does anybody else have opinion on this > patch? I can merge it via my tree but I'd like to get a review from someone > else.
I'm back, actually, and finally had almost crawled from under the pile of mail in mbox. Will apply.
| |