xfs: always take the iolock around xfs_setattr_size
There is no reason to conditionally take the iolock inside xfs_setattr_size when we can let the caller handle it unconditionally, which just incrases the lock hold time for the case where it was previously taken internally by a few instructions. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Ben Myers <bpm@sgi.com>
This commit is contained in:

committed by
Ben Myers

parent
59e5a0e821
commit
76ca4c238c
@@ -38,6 +38,6 @@ extern void xfs_setup_inode(struct xfs_inode *);
|
||||
|
||||
extern int xfs_setattr_nonsize(struct xfs_inode *ip, struct iattr *vap,
|
||||
int flags);
|
||||
extern int xfs_setattr_size(struct xfs_inode *ip, struct iattr *vap, int flags);
|
||||
extern int xfs_setattr_size(struct xfs_inode *ip, struct iattr *vap);
|
||||
|
||||
#endif /* __XFS_IOPS_H__ */
|
||||
|
Reference in New Issue
Block a user