diff options
| author | Jan Kara <jack@suse.cz> | 2009-09-22 04:01:06 +0400 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-09-22 18:17:24 +0400 |
| commit | 580be0837a7a59b207c3d5c661d044d8dd0a6a30 (patch) | |
| tree | 4a659c92ed738367c1ed4d9b1b50fe018f401b81 /Documentation/filesystems | |
| parent | 5be461657be65460ad92be3527e3bb1dd11c49ea (diff) | |
| download | linux-580be0837a7a59b207c3d5c661d044d8dd0a6a30.tar.xz | |
fs: make sure data stored into inode is properly seen before unlocking new inode
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>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/filesystems')
0 files changed, 0 insertions, 0 deletions