mirror of
https://github.com/torvalds/linux.git
synced 2024-11-16 00:52:01 +00:00
4da4b10b5b
It turns out that we only started zeroing a new da btree node's block header on v5 filesystems. Prior to that, we just wouldn't set anything at all, which means that the pad field never got set and would retain whatever happened to be in memory. Therefore, we can only check the pad for zeroness on v5 filesystems. shared/006 on a v4 filesystem exposes this scrub bug. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Reviewed-by: Dave Chinner <dchinner@redhat.com> |
||
---|---|---|
.. | ||
agheader.c | ||
alloc.c | ||
attr.c | ||
bmap.c | ||
btree.c | ||
btree.h | ||
common.c | ||
common.h | ||
dabtree.c | ||
dabtree.h | ||
dir.c | ||
ialloc.c | ||
inode.c | ||
parent.c | ||
quota.c | ||
refcount.c | ||
rmap.c | ||
rtbitmap.c | ||
scrub.c | ||
scrub.h | ||
symlink.c | ||
trace.c | ||
trace.h | ||
xfs_scrub.h |