diff options
| author | Tao Ma <boyu.mt@taobao.com> | 2011-05-18 13:29:57 -0400 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2011-05-18 13:29:57 -0400 |
| commit | ed3ce80a52c4658f48ef8fc825bdedf8b3fcaa89 (patch) | |
| tree | ebed56d680e8d79842b0c3077f11cbc237faa19f /fs/ext4 | |
| parent | 9b940f8e8c32456c8a6428fa4313a4bcca7b4fcb (diff) | |
| download | linux-3.10-ed3ce80a52c4658f48ef8fc825bdedf8b3fcaa89.tar.gz linux-3.10-ed3ce80a52c4658f48ef8fc825bdedf8b3fcaa89.tar.bz2 linux-3.10-ed3ce80a52c4658f48ef8fc825bdedf8b3fcaa89.zip | |
ext4: don't warn about mnt_count if it has been disabled
Currently, if we mkfs a new ext4 volume with s_max_mnt_count set to
zero, and mount it for the first time, we will get the warning:
maximal mount count reached, running e2fsck is recommended
It is really misleading. So change the check so that it won't warn in
that case.
Signed-off-by: Tao Ma <boyu.mt@taobao.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/ext4')
| -rw-r--r-- | fs/ext4/super.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/ext4/super.c b/fs/ext4/super.c index 26893511825..a1f12bab942 100644 --- a/fs/ext4/super.c +++ b/fs/ext4/super.c @@ -1914,7 +1914,7 @@ static int ext4_setup_super(struct super_block *sb, struct ext4_super_block *es, ext4_msg(sb, KERN_WARNING, "warning: mounting fs with errors, " "running e2fsck is recommended"); - else if ((__s16) le16_to_cpu(es->s_max_mnt_count) >= 0 && + else if ((__s16) le16_to_cpu(es->s_max_mnt_count) > 0 && le16_to_cpu(es->s_mnt_count) >= (unsigned short) (__s16) le16_to_cpu(es->s_max_mnt_count)) ext4_msg(sb, KERN_WARNING, |