u-boot.git/fs/ext4, branch v2016.11-rc2

treewide: replace #include with

2016-09-23T21:55:42+00:00

Now, arch/${ARCH}/include/asm/errno.h and include/linux/errno.h have
the same content.  (both just wrap )

Replace all include directives for  with .

Signed-off-by: Masahiro Yamada 
[trini: Fixup include/clk.]
Signed-off-by: Tom Rini

ext4: Revert rejection of 64bit enabled ext4 fs

2016-09-23T13:20:16+00:00

Enable mounting of ext4 fs with 64bit feature, as it is supported now.
These had been disabled in 6f94ab6656ceffb3f2a972c8de4c554502b6f2b7.

Signed-off-by: Stefan Brüns

ext4: Respect group descriptor size when adjusting free counts

2016-09-23T13:20:16+00:00

Also adjust high 16/32 bits when free inode/block counts are modified.

Signed-off-by: Stefan Brüns

ext4: Use helper function to access group descriptor and its fields

2016-09-23T13:20:15+00:00

The descriptor size is variable, thus array indices are not generically
applicable. The larger group descriptors also contain e.g. high parts
of block numbers, which have to be read and written.

Signed-off-by: Stefan Brüns

ext4: Use correct descriptor size when reading the block group descriptor

2016-09-23T13:18:57+00:00

The correct descriptor size must be used when calculating offsets, and
also to read the correct amount of data.

Signed-off-by: Stefan Brüns

ext4: Add helper functions for block group descriptor field access

2016-09-23T13:18:56+00:00

The helper functions encapsulate access of the block group descriptors,
independent of group descriptor size. The helpers also deal with the
endianess of the fields, and with split fields like free_blocks/
free_blocks_high.

Signed-off-by: Stefan Brüns

ext4: determine group descriptor size for 64bit feature

2016-09-23T13:18:56+00:00

If EXT4_FEATURE_INCOMPAT_64BIT is set, the descriptor can be read from
the superblocks, otherwise it defaults to 32.

Signed-off-by: Stefan Brüns

ext4: Fix memory leak of journal buffer if block is updated multiple times

2016-09-23T13:02:44+00:00

If the same block is updated multiple times in a row during a single
file system operation, gd_index is decremented to use the same journal
entry again. Avoid loosing the already allocated buffer.

Signed-off-by: Stefan Brüns

ext4: Correct block number handling, empty block vs. error code

2016-09-23T13:02:44+00:00

read_allocated block may return block number 0, which is just an indicator
a chunk of the file is not backed by a block, i.e. it is sparse.

During file deletions, just continue with the next logical block, for other
operations treat blocknumber <= 0 as an error.

For writes, blocknumber 0 should never happen, as U-Boot always allocates
blocks for the whole file.  Reading already handles this correctly, i.e. the
read buffer is 0-fillled.

Not treating block 0 as sparse block leads to FS corruption, e.g.
	./sandbox/u-boot -c 'host bind 0 ./sandbox/test/fs/3GB.ext4.img ;
		ext4write host 0 0 /2.5GB.file 1 '
The 2.5GB.file from the fs test is actually a sparse file.

Signed-off-by: Stefan Brüns

ext4: remove duplicated block release code for extents

2016-09-23T13:02:43+00:00

The data blocks are identical for files using traditional direct/indirect
block allocation scheme and extent trees, thus this code part can be
common. Only the code to deallocate the indirect blocks to record the
used blocks has to be seperate, respectively the code to release extent
tree index blocks.

Actually the code to release the extent tree index blocks is still missing,
but at least add a FIXME at the appropriate place.

Signed-off-by: Stefan Brüns