xfs: pass inode count through ordered icreate log item
authorBrian Foster <bfoster@redhat.com>
Thu, 28 May 2015 23:05:49 +0000 (09:05 +1000)
committerDave Chinner <david@fromorbit.com>
Thu, 28 May 2015 23:05:49 +0000 (09:05 +1000)
commit463958af5c92d876fd2fe3c756f18bd0ce70b713
treead0faf953226bf32fe4943cc649d42f4eb509c69
parent12d0714d4bdd591d9cd3bce692c831da2c2a0cfc
xfs: pass inode count through ordered icreate log item

v5 superblocks use an ordered log item for logging the initialization of
inode chunks. The icreate log item is currently hardcoded to an inode
count of 64 inodes.

The agbno and extent length are used to initialize the inode chunk from
log recovery. While an incorrect inode count does not lead to bad inode
chunk initialization, we should pass the correct inode count such that log
recovery has enough data to perform meaningful validity checks on the
chunk.

Signed-off-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/xfs/libxfs/xfs_ialloc.c
fs/xfs/libxfs/xfs_ialloc.h
fs/xfs/xfs_log_recover.c