diff options
| author | Eric Sandeen | 2014-02-20 19:32:10 +0100 |
|---|---|---|
| committer | Theodore Ts'o | 2014-02-20 19:32:10 +0100 |
| commit | dc9ddd984df5f5611c7e2149d19be5a8721c1ac5 (patch) | |
| tree | 529e27a9059cff932de90b11e558cca38bfd0e38 /fs/ext4/mballoc.c | |
| parent | ext4: avoid possible overflow in ext4_map_blocks() (diff) | |
| download | kernel-qcow2-linux-dc9ddd984df5f5611c7e2149d19be5a8721c1ac5.tar.gz kernel-qcow2-linux-dc9ddd984df5f5611c7e2149d19be5a8721c1ac5.tar.xz kernel-qcow2-linux-dc9ddd984df5f5611c7e2149d19be5a8721c1ac5.zip | |
ext4: remove unused ac_ex_scanned
When looking at a bug report with:
> kernel: EXT4-fs: 0 scanned, 0 found
I thought wow, 0 scanned, that's odd? But it's not odd; it's printing
a variable that is initialized to 0 and never touched again.
It's never been used since the original merge, so I don't really even
know what the original intent was, either.
If anyone knows how to hook it up, speak now via patch, otherwise just
yank it so it's not making a confusing situation more confusing in
kernel logs.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/ext4/mballoc.c')
| -rw-r--r-- | fs/ext4/mballoc.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c index 0d42f635dda9..a888cac76e9c 100644 --- a/fs/ext4/mballoc.c +++ b/fs/ext4/mballoc.c @@ -4008,8 +4008,7 @@ static void ext4_mb_show_ac(struct ext4_allocation_context *ac) (unsigned long)ac->ac_b_ex.fe_len, (unsigned long)ac->ac_b_ex.fe_logical, (int)ac->ac_criteria); - ext4_msg(ac->ac_sb, KERN_ERR, "%lu scanned, %d found", - ac->ac_ex_scanned, ac->ac_found); + ext4_msg(ac->ac_sb, KERN_ERR, "%d found", ac->ac_found); ext4_msg(ac->ac_sb, KERN_ERR, "groups: "); ngroups = ext4_get_groups_count(sb); for (i = 0; i < ngroups; i++) { |