summaryrefslogtreecommitdiff
path: root/fs/xfs/xfs_alloc_btree.c
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2009-01-19 02:04:16 +0100
committerLachlan McIlroy <lachlan@sgi.com>2009-01-19 14:45:11 +1100
commitb828d8c33867dd6479644c06500975570bfd525c (patch)
tree7788c8a92da9c9859cf40fdd0c1c471debf5035c /fs/xfs/xfs_alloc_btree.c
parent49739140e57a65114d9e1976c4c158d2145595fb (diff)
downloadlinux-3.10-b828d8c33867dd6479644c06500975570bfd525c.tar.gz
linux-3.10-b828d8c33867dd6479644c06500975570bfd525c.tar.bz2
linux-3.10-b828d8c33867dd6479644c06500975570bfd525c.zip
xfs: sanity check attr fork size
Recently we have quite a few kerneloops reports about dereferencing a NULL if_data in the attribute fork. From looking over the code this can only happen if we pass a 0 size argument to xfs_iformat_local. This implies some sort of corruption and in fact the only mailinglist report about this from earlier this year was after a powerfail presumably on a system with write cache and without barriers. Add a quick sanity check for the attr fork size in xfs_iformat to catch these early and without an oops. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'fs/xfs/xfs_alloc_btree.c')
0 files changed, 0 insertions, 0 deletions