summaryrefslogtreecommitdiffstats
path: root/fs/ext4/mballoc.h
diff options
context:
space:
mode:
authorEric Sandeen <sandeen@redhat.com>2014-02-20 13:32:10 -0500
committerTheodore Ts'o <tytso@mit.edu>2014-02-20 13:32:10 -0500
commitdc9ddd984df5f5611c7e2149d19be5a8721c1ac5 (patch)
tree529e27a9059cff932de90b11e558cca38bfd0e38 /fs/ext4/mballoc.h
parente861b5e9a47bd8c6a7491a2b9f6e9a230b1b8e86 (diff)
downloadlinux-dc9ddd984df5f5611c7e2149d19be5a8721c1ac5.tar.gz
linux-dc9ddd984df5f5611c7e2149d19be5a8721c1ac5.tar.bz2
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.h')
-rw-r--r--fs/ext4/mballoc.h2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/ext4/mballoc.h b/fs/ext4/mballoc.h
index 9347328d1cc5..d634e183b4d4 100644
--- a/fs/ext4/mballoc.h
+++ b/fs/ext4/mballoc.h
@@ -175,8 +175,6 @@ struct ext4_allocation_context {
/* copy of the best found extent taken before preallocation efforts */
struct ext4_free_extent ac_f_ex;
- /* number of iterations done. we have to track to limit searching */
- unsigned long ac_ex_scanned;
__u16 ac_groups_scanned;
__u16 ac_found;
__u16 ac_tail;