summaryrefslogtreecommitdiff
path: root/arch/arm/cpu
diff options
context:
space:
mode:
authorIonut Nicu <ioan.nicu.ext@nsn.com>2014-01-13 12:00:08 +0100
committerTom Rini <trini@ti.com>2014-01-20 10:09:40 -0500
commitb5bbac1a9b07016602559ff483df265fef6c1f83 (patch)
treef67b70c37cee3d77b05ea40691081d9c4d1ce60e /arch/arm/cpu
parent470173274d9ceb18a7140ef93e20be6c2236e7d9 (diff)
downloadu-boot-imx-b5bbac1a9b07016602559ff483df265fef6c1f83.zip
u-boot-imx-b5bbac1a9b07016602559ff483df265fef6c1f83.tar.gz
u-boot-imx-b5bbac1a9b07016602559ff483df265fef6c1f83.tar.bz2
ext4fs: fix "invalid extent block" error
For files where we actually have extent indexes following an extent header (ext_block->eh_depth != 0), the do/while loop from ext4fs_get_extent_block() does not select the proper extent index structure. For example, if we have: ext_block->eh_depth = 1 ext_block->eh_entries = 1 fileblock = 0 index[0].ei_block = 0 the do/while loop will exit with i set to 0 and the ext4fs_get_extent_block() function will return 0, even if there was a valid extent index structure following the header. Signed-off-by: Ionut Nicu <ioan.nicu.ext@nsn.com> Signed-off-by: Mathias Rulf <mathias.rulf@nsn.com>
Diffstat (limited to 'arch/arm/cpu')
0 files changed, 0 insertions, 0 deletions