diff options
| author | Jeff Layton <jlayton@redhat.com> | 2011-03-29 09:33:31 -0400 |
|---|---|---|
| committer | Steve French <sfrench@us.ibm.com> | 2011-05-19 14:10:49 +0000 |
| commit | 4358b5678b27ffe81391d84ce150df8e81010f6a (patch) | |
| tree | 7cda0cb7e86e0ecf5a4497c7bb3724a8a2ee6bfd | |
| parent | b73b9a4ba753dfd7d304ee6ee4685b827524c533 (diff) | |
VFS: trivial: fix comment on s_maxbytes value warning check
I originally intended to remove this warning in 2.6.34, but it's not in
a high performance codepath and might help us to catch bugs later. Let's
keep it, but fix the comment to allay confusion about its removal.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Steve French <sfrench@us.ibm.com>
| -rw-r--r-- | fs/super.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/fs/super.c b/fs/super.c index 8a06881b192..c04f7e0b7ed 100644 --- a/fs/super.c +++ b/fs/super.c @@ -948,8 +948,7 @@ mount_fs(struct file_system_type *type, int flags, const char *name, void *data) * filesystems should never set s_maxbytes larger than MAX_LFS_FILESIZE * but s_maxbytes was an unsigned long long for many releases. Throw * this warning for a little while to try and catch filesystems that - * violate this rule. This warning should be either removed or - * converted to a BUG() in 2.6.34. + * violate this rule. */ WARN((sb->s_maxbytes < 0), "%s set sb->s_maxbytes to " "negative value (%lld)\n", type->name, sb->s_maxbytes); |