aboutsummaryrefslogtreecommitdiffstats
path: root/fs/ntfs/usnjrnl.c
diff options
context:
space:
mode:
authorSteven Whitehouse <swhiteho@redhat.com>2011-05-21 09:05:58 -0400
committerSteven Whitehouse <swhiteho@redhat.com>2011-05-21 09:05:58 -0400
commit6d3117b41295150d4ac70622055dd8f5529d86b2 (patch)
tree64a74505be1099c968e1ca47c4fa6a0180cc1ee2 /fs/ntfs/usnjrnl.c
parentc21fd1a8c68ce3f49b00caf10337169262cfb8ad (diff)
GFS2: Wipe directory hash table metadata when deallocating a directory
The deallocation code for directories in GFS2 is largely divided into two parts. The first part deallocates any directory leaf blocks and marks the directory as being a regular file when that is complete. The second stage was identical to deallocating regular files. Regular files have their data blocks in a different address space to directories, and thus what would have been normal data blocks in a regular file (the hash table in a GFS2 directory) were deallocated correctly. However, a reference to these blocks was left in the journal (assuming of course that some previous activity had resulted in those blocks being in the journal or ail list). This patch uses the i_depth as a test of whether the inode is an exhash directory (we cannot test the inode type as that has already been changed to a regular file at this stage in deallocation) The original issue was reported by Chris Hertel as an issue he encountered running bonnie++ Reported-by: Christopher R. Hertel <crh@samba.org> Cc: Abhijith Das <adas@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'fs/ntfs/usnjrnl.c')
0 files changed, 0 insertions, 0 deletions