lkml.org 
[lkml]   [2011]   [Mar]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
FromJeff Layton <>
Subject[PATCH] VFS: remove warning about invalid s_maxbytes values
DateThu, 17 Mar 2011 10:12:43 -0400
This warning should have been removed in 2.6.34. We missed that by a
few releases, so we should be OK to remove this now.

Signed-off-by: Jeff Layton <jlayton@redhat.com>
---
fs/super.c | 10 ----------
1 files changed, 0 insertions(+), 10 deletions(-)
diff --git a/fs/super.c b/fs/super.c
index 7e9dd4c..2ed4a88 100644
--- a/fs/super.c
+++ b/fs/super.c
@@ -1009,16 +1009,6 @@ vfs_kern_mount(struct file_system_type *type, int flags, const char *name, void
if (error)
goto out_sb;

- /*
- * 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.
- */
- WARN((mnt->mnt_sb->s_maxbytes < 0), "%s set sb->s_maxbytes to "
- "negative value (%lld)\n", type->name, mnt->mnt_sb->s_maxbytes);
-
mnt->mnt_mountpoint = mnt->mnt_root;
mnt->mnt_parent = mnt;
up_write(&mnt->mnt_sb->s_umount);
--
1.7.4


\
 
 \ /
  Last update: 2011-03-17 15:15    [from the cache]
©2003-2010