0508986cce
provided the latter is nonzero. At this point, the former is a fairly arbitrary default value (DFTPHYS), so changing it to any reasonable value specified by the device driver is safe. Using the maximum of these limits broke ffs clustered i/o for devices whose si_iosize_max is < DFLTPHYS. Using the minimum would break device drivers' ability to increase the active limit from DFTLPHYS up to MAXPHYS. Copied the code for this and the associated (unnecessary?) fixup of mp_iosize_max to all other filesystems that use clustering (ext2fs and msdosfs). It was completely missing. PR: 36309 MFC-after: 1 week |
||
---|---|---|
.. | ||
COPYRIGHT.INFO | ||
ext2_alloc.c | ||
ext2_balloc.c | ||
ext2_bmap.c | ||
ext2_extern.h | ||
ext2_fs_sb.h | ||
ext2_fs.h | ||
ext2_inode_cnv.c | ||
ext2_inode.c | ||
ext2_linux_balloc.c | ||
ext2_linux_ialloc.c | ||
ext2_lookup.c | ||
ext2_mount.h | ||
ext2_readwrite.c | ||
ext2_subr.c | ||
ext2_vfsops.c | ||
ext2_vnops.c | ||
fs.h | ||
i386-bitops.h | ||
inode.h |