From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Dilger Subject: Re: [PATCH 3/4] vfs: change sb->s_maxbytes to a loff_t Date: Fri, 07 Aug 2009 14:14:47 -0600 Message-ID: <20090807201447.GQ3340@webber.adilger.int> References: <1249671461-9071-1-git-send-email-jlayton@redhat.com> <1249671461-9071-4-git-send-email-jlayton@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, hch@infradead.org, rlove@google.com, msb@google.com, viro@zeniv.linux.org.uk, hannes@cmpxchg.org To: Jeff Layton Return-path: Content-disposition: inline In-reply-to: <1249671461-9071-4-git-send-email-jlayton@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Aug 07, 2009 14:57 -0400, Jeff Layton wrote: > + /* > + * 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 can be removed in 2.6.34. > + */ > + WARN(((unsigned long long) mnt->mnt_sb->s_maxbytes > MAX_LFS_FILESIZE), > + "WARNING: %s sets sb->s_maxbytes too large (%llu)", type->name, > + (unsigned long long) mnt->mnt_sb->s_maxbytes); Rather than removing this check, it should be changed into a BUG_ON() so that no filesystems are added/modified to get it wrong. We hit this problem once in the past also... Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc.