From: Lev Solomonov <solo@primarydata.com>
To: linux-ext4@vger.kernel.org
Cc: Lev Solomonov <solo@primarydata.com>
Subject: [PATCH] debugfs: fix range mode of freei
Date: Wed, 4 Dec 2013 02:14:31 +0200 [thread overview]
Message-ID: <1386116071-4592-1-git-send-email-solo@primarydata.com> (raw)
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 <solo@primarydata.com>
---
debugfs/debugfs.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/debugfs/debugfs.c b/debugfs/debugfs.c
index 8c32eff..cd83ffe 100644
--- a/debugfs/debugfs.c
+++ b/debugfs/debugfs.c
@@ -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);
}
--
1.7.6.5
next reply other threads:[~2013-12-04 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 0:14 Lev Solomonov [this message]
2013-12-05 2:55 ` [PATCH] debugfs: fix range mode of freei Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1386116071-4592-1-git-send-email-solo@primarydata.com \
--to=solo@primarydata.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).