a9b7c63b29
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 |
||
---|---|---|
.. | ||
cd9660_bmap.c | ||
cd9660_lookup.c | ||
cd9660_mount.h | ||
cd9660_node.c | ||
cd9660_node.h | ||
cd9660_rrip.c | ||
cd9660_rrip.h | ||
cd9660_util.c | ||
cd9660_vfsops.c | ||
cd9660_vnops.c | ||
iso_rrip.h | ||
iso.h | ||
TODO | ||
TODO.hibler |