debugfs: fix range mode of freei
PATCH 1/1 debugfs: fix range mode of freei
commit 2ae5d1fdb82b31bf270c4699c59a087c846db2f0 was supposed to teach 'seti' and 'freei' to act on a range of consecutive inodes. apparently only 'seti' has learned: 'freei' doesn't advance the ino, repeatedly acting on the same one instead.
Signed-off-by Lev Solomonov <[email protected]>
--- debugfs/debugfs.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
debugfs/debugfs.c +1 -1
@@ -1042,7 +1042,7 @@ void do_freei(int argc, char *argv[]) !ext2fs_test_inode_bitmap2(current_fs->inode_map,inode))com_err (argv[0 ],0 ,"Warning: inode already clear" );while (len-- >0 ) -ext2fs_unmark_inode_bitmap2 (current_fs->inode_map, inode); +ext2fs_unmark_inode_bitmap2 (current_fs->inode_map, inode++);ext2fs_mark_ib_dirty (current_fs); }
Signature · 1 line
1.7.6.5
Theodore Ts'o
AppliedQuoted 6 lines · Lev Solomonov
commit
2ae5d1fdb82b31bf270c4699c59a087c846db2f0was supposed to teach 'seti' and 'freei' to act on a range of consecutive inodes. apparently only 'seti' has learned: 'freei' doesn't advance the ino, repeatedly acting on the same one instead.Signed-off-by Lev Solomonov <[email protected]>
Applied, thanks.
- Ted