summaryrefslogtreecommitdiffstats
path: root/fs/cramfs
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2020-02-06 17:35:01 -0500
committerTheodore Ts'o <tytso@mit.edu>2020-02-13 11:54:08 -0500
commit4f97a68192bd33b9963b400759cef0ca5963af00 (patch)
tree194a62f440a5f0b7bdaf323b8c9381708344fbcd /fs/cramfs
parent46d36880d1c6f9b9a0cbaf90235355ea1f4cab96 (diff)
downloadlinux-4f97a68192bd33b9963b400759cef0ca5963af00.tar.bz2
ext4: fix support for inode sizes > 1024 bytes
A recent commit, 9803387c55f7 ("ext4: validate the debug_want_extra_isize mount option at parse time"), moved mount-time checks around. One of those changes moved the inode size check before the blocksize variable was set to the blocksize of the file system. After 9803387c55f7 was set to the minimum allowable blocksize, which in practice on most systems would be 1024 bytes. This cuased file systems with inode sizes larger than 1024 bytes to be rejected with a message: EXT4-fs (sdXX): unsupported inode size: 4096 Fixes: 9803387c55f7 ("ext4: validate the debug_want_extra_isize mount option at parse time") Link: https://lore.kernel.org/r/20200206225252.GA3673@mit.edu Reported-by: Herbert Poetzl <herbert@13thfloor.at> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Cc: stable@kernel.org
Diffstat (limited to 'fs/cramfs')
0 files changed, 0 insertions, 0 deletions