summaryrefslogtreecommitdiffstats
path: root/fs/fs-writeback.c
diff options
context:
space:
mode:
authorEric Sandeen <sandeen@redhat.com>2008-08-02 21:21:02 -0400
committerTheodore Ts'o <tytso@mit.edu>2008-08-02 21:21:02 -0400
commite29d1cde63be0b5f1739416b5574a83c34bf8eeb (patch)
tree86f2951e96888a1bd9cdb39ad4b2cb4e88893d95 /fs/fs-writeback.c
parent8a266467b8c4841ca994d0fe59f39e584650e3df (diff)
downloadop-kernel-dev-e29d1cde63be0b5f1739416b5574a83c34bf8eeb.zip
op-kernel-dev-e29d1cde63be0b5f1739416b5574a83c34bf8eeb.tar.gz
ext4: sync up block and inode bitmap reading functions
ext4_read_block_bitmap and read_inode_bitmap do essentially the same thing, and yet they are structured quite differently. I came across this difference while looking at doing bg locking during bg initialization. This patch: * removes unnecessary casts in the error messages * renames read_inode_bitmap to ext4_read_inode_bitmap * and more substantially, restructures the inode bitmap reading function to be more like the block bitmap counterpart. The change to the inode bitmap reader simplifies the locking to be applied in the next patch. Signed-off-by: Eric Sandeen <sandeen@redhat.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/fs-writeback.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud