diff options
| author | Miklos Szeredi <[email protected]> | 2011-05-24 13:06:10 -0700 |
|---|---|---|
| committer | Al Viro <[email protected]> | 2011-05-26 07:26:50 -0400 |
| commit | b5afd2c406f5c6272d916fd705f44f070fbbc0ba (patch) | |
| tree | 93378abaf5120d5fe449ee77234368291331615a /tools/perf/util/scripting-engines/trace-event-perl.c | |
| parent | 5c5d3f3b871a719e2c6413b85009c723adeb27e1 (diff) | |
vfs: fix vfs_rename_dir for FS_RENAME_DOES_D_MOVE filesystems
vfs_rename_dir() doesn't properly account for filesystems with
FS_RENAME_DOES_D_MOVE. If new_dentry has a target inode attached, it
unhashes the new_dentry prior to the rename() iop and rehashes it after,
but doesn't account for the possibility that rename() may have swapped
{old,new}_dentry. For FS_RENAME_DOES_D_MOVE filesystems, it rehashes
new_dentry (now the old renamed-from name, which d_move() expected to go
away), such that a subsequent lookup will find it. Currently all
FS_RENAME_DOES_D_MOVE filesystems compensate for this by failing in
d_revalidate.
The bug was introduced by: commit 349457ccf2592c14bdf13b6706170ae2e94931b1
"[PATCH] Allow file systems to manually d_move() inside of ->rename()"
Fix by not rehashing the new dentry. Rehashing used to be needed by
d_move() but isn't anymore.
Reported-by: Sage Weil <[email protected]>
Signed-off-by: Miklos Szeredi <[email protected]>
Signed-off-by: Al Viro <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-perl.c')
0 files changed, 0 insertions, 0 deletions