ceph: use ihold when we already have an inode ref
We should use ihold whenever we already have a stable inode ref, even
when we aren't holding i_lock. This avoids adding new and unnecessary
locking dependencies.
Signed-off-by:
Sage Weil <sage@newdream.net>
Showing
- fs/ceph/addr.c 1 addition, 1 deletionfs/ceph/addr.c
- fs/ceph/caps.c 4 additions, 6 deletionsfs/ceph/caps.c
- fs/ceph/dir.c 7 additions, 4 deletionsfs/ceph/dir.c
- fs/ceph/export.c 2 additions, 2 deletionsfs/ceph/export.c
- fs/ceph/file.c 2 additions, 1 deletionfs/ceph/file.c
- fs/ceph/inode.c 10 additions, 8 deletionsfs/ceph/inode.c
- fs/ceph/ioctl.c 4 additions, 2 deletionsfs/ceph/ioctl.c
- fs/ceph/locks.c 2 additions, 1 deletionfs/ceph/locks.c
- fs/ceph/snap.c 1 addition, 1 deletionfs/ceph/snap.c
- fs/ceph/xattr.c 4 additions, 2 deletionsfs/ceph/xattr.c
Loading
Please register or sign in to comment