From: Jeff Layton Date: Tue, 29 Mar 2011 13:33:31 +0000 (-0400) Subject: VFS: trivial: fix comment on s_maxbytes value warning check X-Git-Tag: upstream/snapshot3+hdmi~10389^2~22 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=4358b5678b27ffe81391d84ce150df8e81010f6a;p=platform%2Fadaptation%2Frenesas_rcar%2Frenesas_kernel.git 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 Signed-off-by: Steve French --- diff --git a/fs/super.c b/fs/super.c index 8a06881..c04f7e0 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);