mirror of
https://github.com/genesi/linux-legacy.git
synced 2026-02-03 23:54:40 +00:00
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>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
f3408a2d07
commit
2f0ffb7ef7
14
fs/inode.c
14
fs/inode.c
@@ -697,13 +697,15 @@ void unlock_new_inode(struct inode *inode)
|
||||
}
|
||||
#endif
|
||||
/*
|
||||
* This is special! We do not need the spinlock
|
||||
* when clearing I_LOCK, because we're guaranteed
|
||||
* that nobody else tries to do anything about the
|
||||
* state of the inode when it is locked, as we
|
||||
* just created it (so there can be no old holders
|
||||
* that haven't tested I_LOCK).
|
||||
* This is special! We do not need the spinlock when clearing I_LOCK,
|
||||
* because we're guaranteed that nobody else tries to do anything about
|
||||
* the state of the inode when it is locked, as we just created it (so
|
||||
* there can be no old holders that haven't tested I_LOCK).
|
||||
* However we must emit the memory barrier so that other CPUs reliably
|
||||
* see the clearing of I_LOCK after the other inode initialisation has
|
||||
* completed.
|
||||
*/
|
||||
smp_mb();
|
||||
WARN_ON((inode->i_state & (I_LOCK|I_NEW)) != (I_LOCK|I_NEW));
|
||||
inode->i_state &= ~(I_LOCK|I_NEW);
|
||||
wake_up_inode(inode);
|
||||
|
||||
Reference in New Issue
Block a user