u-boot.git/include/ext4fs.h, branch v2017.07

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: 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: 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: Avoid corruption of directories with hash tree indexes

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

While directories can be read using the old linear scan method, adding a
new file would require updating the index tree (alternatively, the whole
tree could be removed).

Signed-off-by: Stefan Brüns 
Reviewed-by: Lukasz Majewski

ext4: fix possible crash on directory traversal, ignore deleted entries

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

The following command triggers a segfault in search_dir:
./sandbox/u-boot -c 'host bind 0 ./sandbox/test/fs/3GB.ext4.img ;
    ext4write host 0 0 /./foo 0x10'

The following command triggers a segfault in check_filename:
./sandbox/u-boot -c 'host bind 0 ./sandbox/test/fs/3GB.ext4.img ;
    ext4write host 0 0 /. 0x10'

"." is the first entry in the directory, thus previous_dir is NULL. The
whole previous_dir block in search_dir seems to be a bad copy from
check_filename(...). As the changed data is not written to disk, the
statement is mostly harmless, save the possible NULL-ptr reference.

Typically a file is unlinked by extending the direntlen of the previous
entry. If the entry is the first entry in the directory block, it is
invalidated by setting inode=0.

The inode==0 case is hard to trigger without crafted filesystems. It only
hits if the first entry in a directory block is deleted and later a lookup
for the entry (by name) is done.

Signed-off-by: Stefan Brüns 
Reviewed-by: Lukasz Majewski

ext4: Refuse to mount filesystems with 64bit feature set

2016-08-05T11:27:14+00:00

With e2fsprogs after 1.43 the 64bit and metadata_csum features are
enabled by default.  The metadata_csum feature changes how
ext4_group_desc->bg_checksum is calculated, which would break write
support.  The 64bit feature however introduces changes such that it
cannot be read by implementations that do not support it.  Since we do
not support this, we must not mount it.

Cc: Stephen Warren 
Cc: Simon Glass 
Cc: Lukasz Majewski 
Cc: Stefan Roese 
Reported-by: Andrew Bradford 
Signed-off-by: Tom Rini

dm: Drop the block_dev_desc_t typedef

2016-03-14T21:34:50+00:00

Use 'struct' instead of a typdef. Also since 'struct block_dev_desc' is long
and causes 80-column violations, rename it to struct blk_desc.

Signed-off-by: Simon Glass 
Reviewed-by: Bin Meng 
Tested-by: Stephen Warren

fs: API changes enabling extra parameter to return size of type loff_t

2014-11-23T11:49:04+00:00

The sandbox/ext4/fat/generic fs commands do not gracefully deal with files
greater than 2GB. Negative values are returned in such cases.

To handle this, the fs functions have been modified to take an additional
parameter of type "* loff_t" which is then populated. The return value
of the fs functions are used only for error conditions.

Signed-off-by: Suriyan Ramasami 
Acked-by: Simon Glass 
[trini: Update board/gdsys/p1022/controlcenterd-id.c,
drivers/fpga/zynqpl.c for changes]
Signed-off-by: Tom Rini

ext4: Prepare API change for files greater than 2GB

2014-11-23T11:49:04+00:00

Change the internal EXT4 functions to use loff_t for offsets.

Signed-off-by: Suriyan Ramasami 
Acked-by: Simon Glass 
[trini: Update common/spl/spl_ext.c]
Signed-off-by: Tom Rini

fs: make it possible to read the filesystem UUID

2014-11-23T11:49:01+00:00

Some filesystems have a UUID stored in its superblock. To
allow using root=UUID=... for the kernel command line we
need a way to read-out the filesystem UUID.

changes rfc -> v1:
 - make the environment variable an option parameter. If not
   given, the UUID is printed out. If given, it is stored in the env
   variable.
 - corrected typos
 - return error codes

changes v1 -> v2:
 - fix return code of do_fs_uuid(..)
 - document do_fs_uuid(..)
 - implement fs_uuid_unsuported(..) be more consistent with the
   way other optional functionality works

changes v2 -> v3:
 - change ext4fs_uuid(..) to make use of #if .. #else .. #endif
   construct to get rid of unreachable code

Hit any key to stop autoboot:  0
=> fsuuid
fsuuid - Look up a filesystem UUID

Usage:
fsuuid  :
    - print filesystem UUID
fsuuid  : 
    - set environment variable to filesystem UUID

=> fsuuid mmc 0:1
d9f9fc05-45ae-4a36-a616-fccce0e4f887
=> fsuuid mmc 0:2
eb3db83c-7b28-499f-95ce-9e0bb21cda81
=> fsuuid mmc 0:1 uuid1
=> fsuuid mmc 0:2 uuid2
=> printenv uuid1
uuid1=d9f9fc05-45ae-4a36-a616-fccce0e4f887
=> printenv uuid2
uuid2=eb3db83c-7b28-499f-95ce-9e0bb21cda81
=>

Signed-off-by: Christian Gmeiner 
Acked-by: Stephen Warren