diff options
| author | Jan Kara <jack@suse.cz> | 2009-09-21 17:01:06 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2009-10-05 08:27:46 -0700 |
| commit | 599312c925523beda5d1c4df834a1d94c57e15ba (patch) | |
| tree | 5af03a331487423de0394c17122df4497c17102e /fs/jfs/xattr.c | |
| parent | 562702289faac232f54b2d2d50ba31646c3d51a5 (diff) | |
fs: make sure data stored into inode is properly seen before unlocking new inode
commit 580be0837a7a59b207c3d5c661d044d8dd0a6a30 upstream.
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.
[akpm@linux-foundation.org: add some commentary]
Signed-off-by: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'fs/jfs/xattr.c')
0 files changed, 0 insertions, 0 deletions