diff options
| author | Icenowy Zheng <icenowy@aosc.io> | 2019-07-25 11:08:52 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-10-17 13:44:47 -0700 |
| commit | 95bcc0d980ae3e2efc2e991d3fb6a1f7e59f6026 (patch) | |
| tree | 5f45cf6d07b1307742aa536b0480b6bce1aaff68 /MAINTAINERS | |
| parent | 7d1688c6731b0d28aefe520414ae85581cc66725 (diff) | |
| download | linux-stable-95bcc0d980ae3e2efc2e991d3fb6a1f7e59f6026.tar.gz linux-stable-95bcc0d980ae3e2efc2e991d3fb6a1f7e59f6026.tar.bz2 linux-stable-95bcc0d980ae3e2efc2e991d3fb6a1f7e59f6026.zip | |
f2fs: use EINVAL for superblock with invalid magic
[ Upstream commit 38fb6d0ea34299d97b031ed64fe994158b6f8eb3 ]
The kernel mount_block_root() function expects -EACESS or -EINVAL for a
unmountable filesystem when trying to mount the root with different
filesystem types.
However, in 5.3-rc1 the behavior when F2FS code cannot find valid block
changed to return -EFSCORRUPTED(-EUCLEAN), and this error code makes
mount_block_root() fail when trying to probe F2FS.
When the magic number of the superblock mismatches, it has a high
probability that it's just not a F2FS. In this case return -EINVAL seems
to be a better result, and this return value can make mount_block_root()
probing work again.
Return -EINVAL when the superblock has magic mismatch, -EFSCORRUPTED in
other cases (the magic matches but the superblock cannot be recognized).
Fixes: 10f966bbf521 ("f2fs: use generic EFSBADCRC/EFSCORRUPTED")
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions