fs-inode_lock-scale-4

Protect inode->i_count with i_lock, rather than having it atomic.
Next step should also be to move things together (eg. the refcount increment
into d_instantiate, which will remove a lock/unlock cycle on i_lock).

Signed-off-by: Nick Piggin <npiggin@suse.de>
Signed-off-by: John Stultz <johnstul@us.ibm.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

1 files changed, 1 insertions, 1 deletions

diff --git a/fs/hpfs/inode.c b/fs/hpfs/inode.c
index fe703ae46bc7..b22044cb988b 100644
--- a/fs/hpfs/inode.c
+++ b/fs/hpfs/inode.c
@@ -182,7 +182,7 @@ void hpfs_write_inode(struct inode *i)
         struct hpfs_inode_info *hpfs_inode = hpfs_i(i);
         struct inode *parent;
         if (i->i_ino == hpfs_sb(i->i_sb)->sb_root) return;
-        if (hpfs_inode->i_rddir_off && !atomic_read(&i->i_count)) {
+        if (hpfs_inode->i_rddir_off && !i->i_count) {
                 if (*hpfs_inode->i_rddir_off) printk("HPFS: write_inode: some position still there\n");
                 kfree(hpfs_inode->i_rddir_off);
                 hpfs_inode->i_rddir_off = NULL;