summaryrefslogtreecommitdiffstats
path: root/fs/jbd2/recovery.c
diff options
context:
space:
mode:
authorDave Chinner <dchinner@redhat.com>2013-09-30 09:37:04 +1000
committerBen Myers <bpm@sgi.com>2013-09-30 17:49:28 -0500
commit367993e7c6428cb7617ab7653d61dca54e2fdede (patch)
tree3e463fde556205e48fe9b01dd4dabb7a249f778e /fs/jbd2/recovery.c
parentf112a049712a5c07de25d511c3c6587a2b1a015e (diff)
downloadlinux-367993e7c6428cb7617ab7653d61dca54e2fdede.tar.bz2
xfs: dirent dtype presence is dependent on directory magic numbers
The determination of whether a directory entry contains a dtype field originally was dependent on the filesystem having CRCs enabled. This meant that the format for dtype beign enabled could be determined by checking the directory block magic number rather than doing a feature bit check. This was useful in that it meant that we didn't need to pass a struct xfs_mount around to functions that were already supplied with a directory block header. Unfortunately, the introduction of dtype fields into the v4 structure via a feature bit meant this "use the directory block magic number" method of discriminating the dirent entry sizes is broken. Hence we need to convert the places that use magic number checks to use feature bit checks so that they work correctly and not by chance. The current code works on v4 filesystems only because the dirent size roundup covers the extra byte needed by the dtype field in the places where this problem occurs. Signed-off-by: Dave Chinner <dchinner@redhat.com> Reviewed-by: Ben Myers <bpm@sgi.com> Signed-off-by: Ben Myers <bpm@sgi.com>
Diffstat (limited to 'fs/jbd2/recovery.c')
0 files changed, 0 insertions, 0 deletions