Searched hist:"463958 af5c92d876fd2fe3c756f18bd0ce70b713" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/fs/xfs/libxfs/ |
H A D | xfs_ialloc.h | diff 463958af5c92d876fd2fe3c756f18bd0ce70b713 Thu May 28 18:05:49 CDT 2015 Brian Foster <bfoster@redhat.com> 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>
|
H A D | xfs_ialloc.c | diff 463958af5c92d876fd2fe3c756f18bd0ce70b713 Thu May 28 18:05:49 CDT 2015 Brian Foster <bfoster@redhat.com> 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>
|
/openbmc/linux/fs/xfs/ |
H A D | xfs_log_recover.c | diff 463958af5c92d876fd2fe3c756f18bd0ce70b713 Thu May 28 18:05:49 CDT 2015 Brian Foster <bfoster@redhat.com> 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>
|