jfs should use MAX_LFS_FILESIZE when calculating s_maxbytes
authorDave Kleikamp <dave.kleikamp@oracle.com>
Thu, 31 Aug 2017 21:46:59 +0000 (16:46 -0500)
committerLinus Torvalds <torvalds@linux-foundation.org>
Fri, 1 Sep 2017 00:02:21 +0000 (17:02 -0700)
commitc227390c91a355300f47f9bef0aefbdfaaca1500
tree0e2d9bd9eb695c55da12ccb7419ca90ccc26ebbd
parent42ff72cf27027fa28dd79acabe01d9196f1480a7
jfs should use MAX_LFS_FILESIZE when calculating s_maxbytes

jfs had previously avoided the use of MAX_LFS_FILESIZE because it hadn't
accounted for the whole 32-bit index range on 32-bit systems.  That has
been fixed by commit 0cc3b0ec23ce ("Clarify (and fix) MAX_LFS_FILESIZE
macros"), so we can simplify the code now.

Suggested by Andreas Dilger.

Signed-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Cc: jfs-discussion@lists.sourceforge.net
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
fs/jfs/super.c