u-boot.git/fs, branch v2017.01

fs/ext4: Initialize group descriptor size for revision level 0 filesystems

2016-12-27T16:24:18+00:00

genext2fs creates revision level 0 filesystems, which are not readable
by u-boot due to the initialized group descriptor size field.
f798b1dda1c5de818b806189e523d1b75db7e72d

Reported-by: Kever Yang 
Reported-by: FrostyBytes@protonmail.com
Signed-off-by: Stefan Brüns 
Tested-by: Kever Yang

fs/fat: simplify get_fatent for FAT12

2016-12-27T16:24:14+00:00

Instead of shuffling bits from two adjacent 16 bit words, use one 16 bit
word with the appropriate byte offset in the buffer.

Signed-off-by: Stefan Brüns

fs/fat: merge readwrite get_fatent_value() with readonly get_fatent()

2016-12-27T16:24:14+00:00

get_fatent_value(...) flushes changed FAT entries to disk when fetching
the next FAT blocks, in every other aspect it is identical to
get_fatent(...).

Provide a stub implementation for flush_dirty_fat_buffer if
CONFIG_FAT_WRITE is not set. Calling flush_dirty_fat_buffer during read
only operation is fine as it checks if any buffers needs flushing.

Signed-off-by: Stefan Brüns 
Reviewed-by: Benoît Thébaudeau

fs/fat: Avoid corruption of sectors following the FAT

2016-12-27T16:24:13+00:00

The FAT is read/flushed in segments of 6 (FATBUFBLOCKS) disk sectors. The
last segment may be less than 6 sectors, cap the length.

Signed-off-by: Stefan Brüns 
Reviewed-by: Benoît Thébaudeau

fat: fatwrite: fix the command for FAT12

2016-12-27T16:24:13+00:00

The u-boot command fatwrite empties FAT clusters from the beginning
till the end of the file.
Specifically for FAT12 it fails to detect the end of the file and goes
beyond the file bounds thus corrupting the file system.

Additionally, FAT entry chaining-up into a file is not implemented
for FAT12.

The users normally workaround this by re-formatting the partition as
FAT16/FAT32, like here:
https://github.com/FEDEVEL/openrex-uboot-v2015.10/issues/1

The patch fixes the bounds of a file and FAT12 entries chaining into
a file, including EOF markup.

Signed-off-by: Philipp Skadorov

sandboxfs: Fix resource leak

2016-12-02T17:37:47+00:00

Now that we free resources in sandbox_fs_ls Coverity is letting us know
that in some cases we might leak.  So in case of error we should still
let os_dirent_free free anything that was allocated.

Fixes: 86167089b71c ("sandbox/fs: Free memory allocated by os_dirent_ls")
Reported-by: Coverity (CID: 153450)
Cc: Stefan Brüns 
Cc: Simon Glass 
Signed-off-by: Tom Rini 
Reviewed-by: Simon Glass

fs/fat/fatwrite: Local variable as buffer to store dir_slot entries

2016-11-29T01:09:45+00:00

fill_dir_slot use get_contents_vfatname_block as a temporary buffer for
constructing a list of dir_slot entries. To save the memory and providing
correct type of memory for above usage, a local buffer with accurate size
declaration is introduced.

The local array size 640 is used because for long file name entry,
each entry use 32 bytes, one entry can store up to 13 characters.
The maximum number of entry possible is 20. So, total size is
32*20=640bytes.

Signed-off-by: Genevieve Chan 
Signed-off-by: Tien Fong Chee

ext4: Allow reading files with non-zero offset, clamp read len

2016-11-21T19:07:27+00:00

Support was already implemented, but not hooked up. This fixes several
fails in the test cases.

Signed-off-by: Stefan Brüns 
Acked-by: Stephen Warren

ext4: Fix handling of sparse files

2016-11-21T19:07:27+00:00

A sparse file may have regions not mapped by any extents, at the start
or at the end of the file, or anywhere between, thus not finding a
matching extent region is never an error.

Found by python filesystem tests.

Signed-off-by: Stefan Brüns

Fix spelling of "multiple".

2016-10-31T14:13:16+00:00

Signed-off-by: Vagrant Cascadian 
Reviewed-by: Simon Glass