| commit | 576a488a27f267af203f3ea69c700a1612335e9f | |
| author | Dave Chinner <david@fromorbit.com> | |
| Wed, 3 Dec 2008 22:09:34 +0000 (4 09:09 +1100) | ||
| committer | Lachlan McIlroy <lachlan@redback.melbourne.sgi.com> | |
| Fri, 5 Dec 2008 04:39:13 +0000 (5 15:39 +1100) | ||
| tree | 8c2cad9d20c5153a3eaa0b7f0b9259ac9a4fd676 | treesnapshot (tar.gz zip) |
| parent | feaf3848a813a106f163013af6fcf6c4bfec92d9 | commitdiff |
[XFS] Fix hang after disallowed rename across directory quota domains
When project quota is active and is being used for directory tree
quota control, we disallow rename outside the current directory
tree. This requires a check to be made after all the inodes
involved in the rename are locked. We fail to unlock the inodes
correctly if we disallow the rename when the target is outside the
current directory tree. This results in a hang on the next access
to the inodes involved in failed rename.
Reported-by: Arkadiusz Miskiewicz <arekm@maven.pl>
Signed-off-by: Dave Chinner <david@fromorbit.com>
Tested-by: Arkadiusz Miskiewicz <arekm@maven.pl>
Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
When project quota is active and is being used for directory tree
quota control, we disallow rename outside the current directory
tree. This requires a check to be made after all the inodes
involved in the rename are locked. We fail to unlock the inodes
correctly if we disallow the rename when the target is outside the
current directory tree. This results in a hang on the next access
to the inodes involved in failed rename.
Reported-by: Arkadiusz Miskiewicz <arekm@maven.pl>
Signed-off-by: Dave Chinner <david@fromorbit.com>
Tested-by: Arkadiusz Miskiewicz <arekm@maven.pl>
Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
| fs/xfs/xfs_rename.c | diffblobblamehistory |