diff options
| author | Sean Anderson <seanga2@gmail.com> | 2023-09-30 16:42:46 -0400 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2023-10-17 20:50:52 -0400 |
| commit | bfcf7521eb73a0a38412307f6a398a0ae0d1b10d (patch) | |
| tree | 56db9bf81ab47fd3bba8385772758999d4cba10e | |
| parent | a0733b3c66fceba34e5fad2c84ccbfa79ede00f3 (diff) | |
| download | u-boot-bfcf7521eb73a0a38412307f6a398a0ae0d1b10d.zip u-boot-bfcf7521eb73a0a38412307f6a398a0ae0d1b10d.tar.gz u-boot-bfcf7521eb73a0a38412307f6a398a0ae0d1b10d.tar.bz2 | |
Revert "fs: ext4: check the minimal partition size to mount"
This check breaks small partitions (under 1024 blocks) because part_length
is in units of part.blksz and not bytes. Given the purpose of this
function, we really want to make sure the partition is SUPERBLOCK_START +
SUPERBLOCK_SIZE (2048) bytes so we can call ext4_read_superblock without
error.
The obvious solution is to convert callers from things like
ext4fs_mount(part_info.size)
to
ext4fs_mount(part_info.size * part_info.blksz);
However, I'm not really a fan of the bloat that would cause, especially
since the error is now suppressed. I think the best course of action here
is to just revert the patch.
This reverts commit 9905cae65e03335aefcb1ebfab5b7ee62d89f64e.
Signed-off-by: Sean Anderson <seanga2@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
| -rw-r--r-- | fs/ext4/ext4_common.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/fs/ext4/ext4_common.c b/fs/ext4/ext4_common.c index 9a9c520..f50de7c 100644 --- a/fs/ext4/ext4_common.c +++ b/fs/ext4/ext4_common.c @@ -2373,10 +2373,6 @@ int ext4fs_mount(unsigned part_length) struct ext2_data *data; int status; struct ext_filesystem *fs = get_fs(); - - if (part_length < SUPERBLOCK_SIZE) - return 0; - data = zalloc(SUPERBLOCK_SIZE); if (!data) return 0; |