u-boot.git/fs, branch v2015.01-rc2

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

sandbox: Prepare API change for files greater than 2GB

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

Change the internal sandbox functions to use loff_t for file offsets.

Signed-off-by: Suriyan Ramasami 

Acked-by: Simon Glass

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

fat: Prepare API change for files greater than 2GB

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

Change the internal FAT functions to use loff_t for offsets.

Signed-off-by: Suriyan Ramasami 
Acked-by: Simon Glass 
[trini: Fix fs/fat/fat.c for min3 updates]
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

linux/kernel.h: sync min, max, min3, max3 macros with Linux

2014-11-23T11:48:30+00:00

U-Boot has never cared about the type when we get max/min of two
values, but Linux Kernel does.  This commit gets min, max, min3, max3
macros synced with the kernel introducing type checks.

Many of references of those macros must be fixed to suppress warnings.
We have two options:
 - Use min, max, min3, max3 only when the arguments have the same type
   (or add casts to the arguments)
 - Use min_t/max_t instead with the appropriate type for the first
   argument

Signed-off-by: Masahiro Yamada 
Acked-by: Pavel Machek 
Acked-by: Lukasz Majewski 
Tested-by: Lukasz Majewski 
[trini: Fixup arch/blackfin/lib/string.c]
Signed-off-by: Tom Rini

include: move various macros to include/linux/kernel.h

2014-11-20T16:28:25+00:00

U-Boot has imported various utility macros from Linux
scattering them to various places without consistency.

In include/common.h are min, max, min3, max3, ARRAY_SIZE, ALIGN,
container_of, DIV_ROUND_UP, etc.
In include/linux/compat.h are min_t, max_t, round_up, round_down,
etc.
We also have duplicated defines of min_t in some *.c files.

Moreover, we are suffering from too cluttered include/common.h.

This commit moves various macros that originate in
include/linux/kernel.h of Linux to their original position.

Note:
This commit simply moves the macros; the macros roundup,
min, max, min2, max3, ARRAY_SIZE are different
from those of Linux at this point.

Signed-off-by: Masahiro Yamada

ZFS: Clean up cppcheck warnings where relevant, leaked memory etc

2014-11-10T21:25:27+00:00

In a message from Wolfgang Denk highlighting warnings from cppcheck,
the patch will address those that are correctly diagnosed. Some are
false-positives:

> [fs/zfs/zfs.c:937]: (error) Memory leak: l
dmu_read() allocates "l" if successful, so error-case should not free
it.
> [fs/zfs/zfs.c:1141]: (error) Memory leak: dnbuf
dmu_read() allocates "dnbuf" if successful, so error-case should not
free it.
> [fs/zfs/zfs.c:1372]: (error) Memory leak: osp
zio_read() allocates "osp" if successful, so error-case should
not free it.
> [fs/zfs/zfs.c:1726]: (error) Memory leak: nvlist
int_zfs_fetch_nvlist() allocates "nvlist" if successful, so error-case
should not free it.

Signed-off-by: Jorgen Lundman

spl: Add EXT support to SPL

2014-10-27T21:54:03+00:00

Add EXT filesystem support to SPL.

Signed-off-by: Guillaume GARDET 
[trini: Fix a warning and checkpatch problems]
Signed-off-by: Tom Rini

ext4: Use inttypes for printf() string

2014-10-27T15:04:01+00:00

On 64-bit platforms (like sandbox) 64-bit integers may be 'long' rather
than 'long long'. Use the inttypes header to avoid compiler warnings.

Signed-off-by: Simon Glass