> from fs/udf/super.c:
> in function udf_fill_super
> sb->s_maxbytes = 1<<30; (1 GB)
>
> Why sb->s_maxbytes is not equal to MAX_LFS_FILESIZE?
Because UDF had some flaws and user could crash a kernel with larger
filesize. In -mm kernel are patches fixing the flaw and also raising the
limit back to MAX_LFS_FILESIZE.
> So, in include/linux/fs.h written that the filesystems should put that
> (MAX_LFS_FILESIZE) into their s_maxbytes, otherwise bad things can
> happen in VM.
Bad things can happen only if you set it to more than
MAX_LFS_FILESIZE. With smaller values only users are disappointed ;).
Honza
--
Jan Kara <[email protected]>
SuSE CR Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]