diff options
| author | Fabian Frederick <fabf@skynet.be> | 2017-01-18 19:39:35 +0100 |
|---|---|---|
| committer | Jan Kara <jack@suse.cz> | 2017-01-20 12:21:41 +0100 |
| commit | 70f16cef06b5bf72d50b8016e1188995eddc073a (patch) | |
| tree | 3ce4492971a2d06aa84381634dba1593691a52ad /crypto/ccm.c | |
| parent | 1d82a56bc5bf820b7c65d8130b44c0bc101b546c (diff) | |
udf: allow implicit blocksize specification during mount
udf_fill_super() used udf_parse_options() to flag UDF_FLAG_BLOCKSIZE_SET
when blocksize was specified otherwise used 512 bytes
(bdev_logical_block_size) and 2048 bytes (UDF_DEFAULT_BLOCKSIZE)
IOW both 1024 and 4096 specifications were required or resulted in
"mount: wrong fs type, bad option, bad superblock on /dev/loop1"
This patch loops through different block values but also updates
udf_load_vrs() to return -EINVAL instead of 0 when udf_check_vsd()
fails (and uopt->novrs = 0).
The later being the reason for the RFC; we have that case when mounting
a 4kb blocksize against other values but maybe VRS is not mandatory
there ?
Tested with 512, 1024, 2048 and 4096 blocksize
Reported-by: Jan Kara <jack@suse.com>
Signed-off-by: Fabian Frederick <fabf@skynet.be>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'crypto/ccm.c')
0 files changed, 0 insertions, 0 deletions