[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <20090807201447.GQ3340@webber.adilger.int>
Date: Fri, 07 Aug 2009 14:14:47 -0600
From: Andreas Dilger <adilger@....com>
To: Jeff Layton <jlayton@...hat.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, hch@...radead.org, rlove@...gle.com,
msb@...gle.com, viro@...iv.linux.org.uk, hannes@...xchg.org
Subject: Re: [PATCH 3/4] vfs: change sb->s_maxbytes to a loff_t
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists